Triple
T30653385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eje 1 Sur |
E780319
|
entity |
| Predicate | trafficFlowType |
P27465
|
FINISHED |
| Object | high-capacity corridor |
—
|
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: high-capacity corridor | Statement: [Eje 1 Sur, trafficFlowType, high-capacity corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficFlowType Context triple: [Eje 1 Sur, trafficFlowType, high-capacity corridor]
-
A.
trafficType
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
-
B.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
C.
coversTrafficType
Indicates that one entity includes, handles, or applies to a specified type or category of traffic.
-
D.
majorTrafficType
chosen
Indicates the primary kind of traffic or flow that predominantly characterizes a given route, segment, or transportation context.
-
E.
routesTrafficThrough
Indicates that network traffic originating from one entity is directed to pass through another entity as an intermediate path or conduit.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a99479c81908ec9b70fe5b025f7 |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:30 p.m.