Triple
T16655837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leavenworth |
E404725
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Lansing, Kansas |
E103517
|
NE 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: Lansing, Kansas | Statement: [Leavenworth, adjacentTo, Lansing, Kansas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lansing, Kansas Context triple: [Leavenworth, adjacentTo, Lansing, Kansas]
-
A.
Lansing, Kansas
chosen
Lansing, Kansas is a small city in Leavenworth County known for housing the Lansing Correctional Facility and serving as part of the greater Kansas City metropolitan area.
-
B.
Wellington, Kansas
Wellington, Kansas is a small city in south-central Kansas known historically as a regional agricultural and railroad hub.
-
C.
Louisville, Kansas
Louisville, Kansas is a small rural community in Pottawatomie County that forms part of the Manhattan, Kansas region.
-
D.
Hartford, Kansas
Hartford, Kansas is a small rural city in east-central Kansas known for its close-knit community and agricultural surroundings.
-
E.
Madison, Kansas
Madison, Kansas is a small rural city in Greenwood County known for its agricultural surroundings and location in east-central Kansas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfa45d8819081bf8579a7160389 |
completed | April 18, 2026, 12:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00a50edea48190b65f4e6a9eb3ba24 |
completed | May 10, 2026, 3:32 p.m. |
Created at: April 10, 2026, 5:18 a.m.