Triple
T16961919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana circuit courts |
E411450
|
entity |
| Predicate | isPrimaryTrialCourt |
P12546
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Indiana circuit courts, isPrimaryTrialCourt, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryTrialCourt Context triple: [Indiana circuit courts, isPrimaryTrialCourt, yes]
-
A.
hasTrialCourtLevel
Indicates the specific level or tier within the judicial hierarchy at which a trial court operates.
-
B.
jurisdictionOfPrimaryCourt
Indicates the geographic or legal scope within which a primary court has the authority to hear and decide cases.
-
C.
isMajorCourtIn
chosen
Indicates that a court is a primary or high-level judicial body within the specified jurisdiction or region.
-
D.
isCourtOfRecord
Indicates that a particular court maintains a permanent, authoritative record of its proceedings and has the power to fine or imprison for contempt.
-
E.
highestTrialCourtOf
Indicates that one entity serves as the supreme or final-level trial court within the judicial hierarchy of another entity (such as a jurisdiction or legal system).
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d021c5508190b6e3106554c07a9c |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.