Triple
T38076815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska Crossing |
E950738
|
entity |
| Predicate | distanceFromOmaha |
P76348
|
FINISHED |
| Object | approximately 20 miles southwest of Omaha |
—
|
LITERAL 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: approximately 20 miles southwest of Omaha | Statement: [Nebraska Crossing, distanceFromOmaha, approximately 20 miles southwest of Omaha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromOmaha Context triple: [Nebraska Crossing, distanceFromOmaha, approximately 20 miles southwest of Omaha]
-
A.
distanceToOmaha
chosen
Indicates the spatial distance between a given entity’s location and the location of Omaha.
-
B.
distanceToOklahomaCity
Indicates the spatial distance between a given entity’s location and the location of Oklahoma City.
-
C.
distanceFromDesMoines
Indicates the physical distance between a given location and the city of Des Moines.
-
D.
distanceToWichita
Indicates the measured distance between a given entity’s location and the city of Wichita.
-
E.
distanceFromUrbana
Indicates the measured spatial distance between a given entity or location and Urbana.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.