Triple
T33850699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston Premium Outlets |
E867613
|
entity |
| Predicate | distanceFromHoustonDowntown |
P108385
|
FINISHED |
| Object | approximately 30 miles northwest |
—
|
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 30 miles northwest | Statement: [Houston Premium Outlets, distanceFromHoustonDowntown, approximately 30 miles northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromHoustonDowntown Context triple: [Houston Premium Outlets, distanceFromHoustonDowntown, approximately 30 miles northwest]
-
A.
distanceToHouston
chosen
Indicates the physical distance between a given location or entity and the city of Houston.
-
B.
distanceFromDallas
Indicates the measured distance between a given place or entity and the city of Dallas.
-
C.
distanceToAustin
Indicates the spatial distance between a given entity or location and the city of Austin.
-
D.
distanceFromSanAntonio
Indicates the measured or specified distance between an entity and the location of San Antonio.
-
E.
directionFromHouston
Indicates the cardinal or relative compass direction of one location as measured from Houston.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:47 a.m.