Triple
T13141586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Jackson, Texas |
E312221
|
entity |
| Predicate | distanceToHouston |
P108385
|
FINISHED |
| Object | approximately 50 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 50 miles south | Statement: [Lake Jackson, Texas, distanceToHouston, approximately 50 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToHouston Context triple: [Lake Jackson, Texas, distanceToHouston, approximately 50 miles south]
-
A.
distanceToAustin
Indicates the spatial distance between a given entity or location and the city of Austin.
-
B.
distanceFromDallas
Indicates the measured distance between a given place or entity and the city of Dallas.
-
C.
distanceFromSanAntonio
Indicates the measured or specified distance between an entity and the location of San Antonio.
-
D.
distanceToGalveston
Indicates the measured distance between a given location or entity and Galveston.
-
E.
distanceToAmarillo
Indicates the spatial distance between a given entity and the location Amarillo.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b84f1081908b9e2d54a64d4c2d |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d980e622e8819087a69bfb1660dd64 |
completed | April 10, 2026, 10:59 p.m. |
Created at: April 9, 2026, 9:10 p.m.