Triple
T18858564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 135 |
E461242
|
entity |
| Predicate | servesCity |
P82
|
FINISHED |
| Object | Newton, 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: Newton, Kansas | Statement: [Interstate 135, servesCity, Newton, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Newton, Kansas Context triple: [Interstate 135, servesCity, Newton, Kansas]
-
A.
Newton, Kansas
chosen
Newton, Kansas is a small city in south-central Kansas known historically as a railroad hub and gateway to the American West.
-
B.
Wellington, Kansas
Wellington, Kansas is a small city in south-central Kansas known historically as a regional agricultural and railroad hub.
-
C.
Watson, Kansas
Watson, Kansas is a small unincorporated rural community located in Shawnee County in the U.S. state of Kansas.
-
D.
Madison, Kansas
Madison, Kansas is a small rural city in Greenwood County known for its agricultural surroundings and location in east-central Kansas.
-
E.
St. Paul, Kansas
St. Paul, Kansas is a small rural city in southeastern Kansas known for its strong Catholic heritage and historic mission roots.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05eaee881909da704cf1374158c |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 10, 2026, 11:57 a.m.