Triple
T20055514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-335 |
E499320
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Emporia, Kansas |
—
|
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: Emporia, Kansas | Statement: [I-335, connects, Emporia, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Emporia, Kansas Context triple: [I-335, connects, Emporia, Kansas]
-
A.
Emporia, Kansas
chosen
Emporia, Kansas is a small city in east-central Kansas known as a regional hub for education, commerce, and transportation on the Great Plains.
-
B.
Wellington, Kansas
Wellington, Kansas is a small city in south-central Kansas known historically as a regional agricultural and railroad hub.
-
C.
St. Paul, Kansas
St. Paul, Kansas is a small rural city in southeastern Kansas known for its strong Catholic heritage and historic mission roots.
-
D.
Eudora, Kansas
Eudora, Kansas is a small city in northeastern Kansas located between Lawrence and the Kansas City metropolitan area.
-
E.
Peabody, Kansas
Peabody, Kansas is a small historic city in central Kansas known for its 19th-century architecture and annual Independence Day celebrations.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66332b300819097f5dca1636e5822 |
completed | April 20, 2026, 5:32 p.m. |
Created at: April 11, 2026, 3:38 p.m.