Triple
T8867774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pantego, Texas |
E211061
|
entity |
| Predicate | regionalProximity |
P55639
|
FINISHED |
| Object | west of Dallas, Texas |
—
|
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: west of Dallas, Texas | Statement: [Pantego, Texas, regionalProximity, west of Dallas, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalProximity Context triple: [Pantego, Texas, regionalProximity, west of Dallas, Texas]
-
A.
featuresRegionalProximity
chosen
Indicates that one entity is located near or in close geographic proximity to a particular region or another entity.
-
B.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
C.
hasNearbyCityArea
Indicates that one area is geographically close to or adjacent to a city area.
-
D.
residesNear
Indicates that one entity lives or is located in close physical proximity to another entity.
-
E.
hasRegionalCenterNearby
Indicates that a regional center is located in close proximity to the referenced entity.
- F. None of above.
Provenance (3 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61241d048190aead14a8f5589856 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:51 p.m.