Triple
T30004456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brady, Texas |
E762266
|
entity |
| Predicate | distanceFromSanAngelo |
P202831
|
FINISHED |
| Object | approximately 75 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: approximately 75 miles east | Statement: [Brady, Texas, distanceFromSanAngelo, approximately 75 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSanAngelo Context triple: [Brady, Texas, distanceFromSanAngelo, approximately 75 miles east]
-
A.
distanceFromSanAntonio
Indicates the measured or specified distance between an entity and the location of San Antonio.
-
B.
distanceToAmarillo
Indicates the spatial distance between a given entity and the location Amarillo.
-
C.
distanceFromDallas
Indicates the measured distance between a given place or entity and the city of Dallas.
-
D.
approximateDistanceToElPaso
Indicates that one entity has an estimated or rough distance measurement relative to the location of El Paso.
-
E.
distanceToAustin
Indicates the spatial distance between a given entity or location and the city of Austin.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00c3362dcc819096e49b882709fddd |
completed | May 10, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_6a00c2e5cdd88190a5f2d0f6a843cd56 |
completed | May 10, 2026, 5:39 p.m. |
| PDg | Predicate description generation | batch_6a00c3355498819088253d5e5c17267f |
completed | May 10, 2026, 5:41 p.m. |
Created at: April 29, 2026, 6:42 p.m.