Triple
T35827692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chireno, Texas |
E1035694
|
entity |
| Predicate | distanceToNacogdoches |
P206070
|
FINISHED |
| Object | about 17 miles east |
—
|
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: about 17 miles east | Statement: [Chireno, Texas, distanceToNacogdoches, about 17 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNacogdoches Context triple: [Chireno, Texas, distanceToNacogdoches, about 17 miles east]
-
A.
distanceToMontgomery
Indicates the spatial distance between a given entity and the location identified as Montgomery.
-
B.
distanceToGalveston
Indicates the measured distance between a given location or entity and Galveston.
-
C.
distanceToTexarkana
Indicates the physical distance between a given location and the city of Texarkana.
-
D.
distanceToHouston
Indicates the physical distance between a given location or entity and the city of Houston.
-
E.
distanceToHuntsville
Indicates the measured distance between a given entity and the location Huntsville.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.