Triple
T21680174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 19th Judicial Circuit of Missouri |
E535082
|
entity |
| Predicate | hasTrialCourtStatus |
P50738
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [19th Judicial Circuit of Missouri, hasTrialCourtStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrialCourtStatus Context triple: [19th Judicial Circuit of Missouri, hasTrialCourtStatus, true]
-
A.
hasTrialCourtLevel
Indicates the specific level or tier within the judicial hierarchy at which a trial court operates.
-
B.
hasTribunal
Indicates that an entity is associated with or subject to a specific tribunal, such as a court or adjudicative body, that has authority over its cases or matters.
-
C.
courtStatus
chosen
Indicates the current legal or procedural state of a case or matter within a court system.
-
D.
onTrialFor
Indicates that a person is currently being legally prosecuted or judged in court for a specific alleged offense or charge.
-
E.
hasStateCourt
Indicates that a given jurisdiction or region possesses an official court that operates at the state level.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a12adf08190b9b450eb26a1f33c |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:43 p.m.