Triple
T25942064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westheimer Road |
E653730
|
entity |
| Predicate | isEconomicCorridorOf |
P77611
|
FINISHED |
| Object | Houston |
—
|
NE NERFINISHED |
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: Houston | Statement: [Westheimer Road, isEconomicCorridorOf, Houston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEconomicCorridorOf Context triple: [Westheimer Road, isEconomicCorridorOf, Houston]
-
A.
partOfEconomicCorridor
chosen
Indicates that one entity is included within, or constitutes a segment of, a larger defined economic corridor.
-
B.
shareEconomicCorridor
Indicates that two or more entities are connected by, or participate in, the same economic corridor for trade, transport, or development activities.
-
C.
mainEconomicCorridorOf
Indicates that one entity serves as the primary economic corridor or principal route for trade and economic activity of another entity.
-
D.
isIndustrialCorridor
Indicates that an area or route is designated and used primarily for industrial activities, facilities, or transportation.
-
E.
locatedInTransportCorridor
Indicates that an entity is situated within a designated transport corridor used for the movement of people or goods.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6045ec5708190917d60774389e68c |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:40 a.m.