Triple
T8694963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple, Texas |
E206383
|
entity |
| Predicate | distanceToAustin |
P84239
|
FINISHED |
| Object | approximately 65 miles north |
—
|
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 65 miles north | Statement: [Temple, Texas, distanceToAustin, approximately 65 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAustin Context triple: [Temple, Texas, distanceToAustin, approximately 65 miles north]
-
A.
distanceFromDallas
Indicates the measured distance between a given place or entity and the city of Dallas.
-
B.
distanceToPhoenix
Indicates the measured or estimated distance between a given entity’s location and the city of Phoenix.
-
C.
distanceToLosAngeles
Indicates the measured or calculated distance between a given entity’s location and the city of Los Angeles.
-
D.
distanceToSeattle
Indicates the measured or calculated distance between a given entity’s location and the city of Seattle.
-
E.
distanceFromLosAngeles
Indicates the measured or specified distance between a given entity’s location and the city of Los Angeles.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58284c58819091beb05a7d6b3a1b |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc483f06f48190879f4702c8b4ed00 |
completed | March 31, 2026, 10:18 p.m. |
Created at: March 30, 2026, 6:33 p.m.