Triple
T35421378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biggsville, Illinois |
E1023802
|
entity |
| Predicate | isInStateLevel |
P31574
|
FINISHED |
| Object | Illinois |
—
|
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: Illinois | Statement: [Biggsville, Illinois, isInStateLevel, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInStateLevel Context triple: [Biggsville, Illinois, isInStateLevel, Illinois]
-
A.
isInStateLevelEntity
Indicates that one entity is located within, or falls under the jurisdiction of, a state-level administrative or governmental entity.
-
B.
hasStateOrDistrict
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
-
C.
isInProvince
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
-
D.
isInUSState
chosen
Indicates that one entity (typically a place or location) is geographically located within the boundaries of a specific U.S. state.
-
E.
stateLevelRepresentation
Indicates that an entity serves as a representative or representation at the level of a state (subnational government 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.