Triple
T9709093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okmulgee, Oklahoma |
E234974
|
entity |
| Predicate | distanceToTulsa |
P90373
|
FINISHED |
| Object | approximately 40 miles south |
—
|
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 40 miles south | Statement: [Okmulgee, Oklahoma, distanceToTulsa, approximately 40 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTulsa Context triple: [Okmulgee, Oklahoma, distanceToTulsa, approximately 40 miles south]
-
A.
distanceToOklahomaCity
Indicates the spatial distance between a given entity’s location and the location of Oklahoma City.
-
B.
distanceToWichita
Indicates the measured distance between a given entity’s location and the city of Wichita.
-
C.
distanceFromDallas
Indicates the measured distance between a given place or entity and the city of Dallas.
-
D.
distanceToOmaha
Indicates the spatial distance between a given entity’s location and the location of Omaha.
-
E.
distanceToKansasCity
Indicates the spatial distance between a given location or entity and Kansas City.
- F. None of above. chosen
Provenance (4 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da7c6188190b086f7e411378268 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:19 p.m.