Triple
T35458491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 10 in Houston |
E1024845
|
entity |
| Predicate | hasJunctionComplex |
P38489
|
FINISHED |
| Object | I-10/I-45/I-69 Downtown Houston interchange |
—
|
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: I-10/I-45/I-69 Downtown Houston interchange | Statement: [Interstate 10 in Houston, hasJunctionComplex, I-10/I-45/I-69 Downtown Houston interchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJunctionComplex Context triple: [Interstate 10 in Houston, hasJunctionComplex, I-10/I-45/I-69 Downtown Houston interchange]
-
A.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
B.
hasJunctionIn
chosen
Indicates that one entity contains or includes a junction located within the spatial or structural extent of another entity.
-
C.
hasJunctionType
Indicates the specific kind or classification of a junction associated with an entity.
-
D.
hasJunctionCount
Indicates the number of junctions associated with or contained in a given entity.
-
E.
hasJunctionFunction
Indicates that one entity serves as a junction or connecting function for another entity within a system or structure.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.