Triple
T27647207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Probate Division |
E696742
|
entity |
| Predicate | parentCourtType |
P8214
|
FINISHED |
| Object | trial court |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: trial court | Statement: [Probate Division, parentCourtType, trial court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCourtType Context triple: [Probate Division, parentCourtType, trial court]
-
A.
parentCourt
Indicates that one court is hierarchically above and has authority over another court within a judicial system.
-
B.
hasTypeOfCourt
chosen
Indicates that an entity is associated with or classified by a specific type or category of court.
-
C.
jurisdictionOfPrimaryCourt
Indicates the geographic or legal scope within which a primary court has the authority to hear and decide cases.
-
D.
parentDetermination
Indicates that one entity is responsible for determining, designating, or establishing the parent or parental status of another entity.
-
E.
priorCourt
Indicates that one court or legal proceeding occurred before another in time or procedural sequence.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 2:30 p.m.