Triple
T30803355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulphur, Oklahoma |
E784431
|
entity |
| Predicate | distanceToDallasFortWorth |
P203318
|
FINISHED |
| Object | approximately 140 miles |
—
|
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 140 miles | Statement: [Sulphur, Oklahoma, distanceToDallasFortWorth, approximately 140 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDallasFortWorth Context triple: [Sulphur, Oklahoma, distanceToDallasFortWorth, approximately 140 miles]
-
A.
distanceToFortWorth
Indicates the spatial distance between a given location and the city of Fort Worth.
-
B.
distanceFromDallas
Indicates the measured distance between a given place or entity and the city of Dallas.
-
C.
distanceToFortWorth_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Fort Worth.
-
D.
distanceToAustin
Indicates the spatial distance between a given entity or location and the city of Austin.
-
E.
distanceToHouston
Indicates the physical distance between a given location or entity and the city of Houston.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0154b16a3c8190b808a460ae3a91ac |
completed | May 11, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a01539f19d88190b2de63f5262b1074 |
completed | May 11, 2026, 3:57 a.m. |
| PDg | Predicate description generation | batch_6a0154b0a9e48190ae747136b4587ceb |
completed | May 11, 2026, 4:01 a.m. |
Created at: April 29, 2026, 8:42 p.m.