Triple
T31910599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milo, Missouri |
E814671
|
entity |
| Predicate | fallsUnderStateJurisdiction |
P111476
|
FINISHED |
| Object | Missouri |
—
|
NE NERFINISHED |
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: Missouri | Statement: [Milo, Missouri, fallsUnderStateJurisdiction, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fallsUnderStateJurisdiction Context triple: [Milo, Missouri, fallsUnderStateJurisdiction, Missouri]
-
A.
fallsUnderLaw
Indicates that one entity is subject to, governed by, or regulated under a particular law or legal provision.
-
B.
fallsUnderStateElectionAuthority
Indicates that the subject is governed, regulated, or overseen by a state-level election authority.
-
C.
territorialJurisdictionIncludes
chosen
Indicates that one authority’s territorial jurisdiction encompasses or extends over a specified geographic area or location.
-
D.
hasPoliticalJurisdictionType
Indicates the type or category of political jurisdiction that applies to or governs an entity.
-
E.
usesJurisdiction
Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1ba24c48190845437eb7d691a1e |
completed | May 3, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:01 a.m.