Triple
T18150905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MoPac Expressway |
E434497
|
entity |
| Predicate | runsAlongSideOf |
P31095
|
FINISHED |
| Object | western side of Austin |
—
|
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: western side of Austin | Statement: [MoPac Expressway, runsAlongSideOf, western side of Austin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsAlongSideOf Context triple: [MoPac Expressway, runsAlongSideOf, western side of Austin]
-
A.
operatedAlongside
Indicates that two or more entities functioned or were active together in a coordinated or concurrent manner within the same context or system.
-
B.
builtAlongside
Indicates that one entity was constructed next to or in parallel with another entity, typically during the same or a closely related time period.
-
C.
passedAlongside
Indicates that one entity moved or traveled next to another entity along the same route or path, maintaining a roughly parallel course.
-
D.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
E.
appearsAlongside
Indicates that two entities are present or occur together in the same context, setting, or instance.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de3812e8819097f025476d5c6a1d |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.