Triple
T25803112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bovaird Drive corridor |
E649889
|
entity |
| Predicate | primaryDirectionServed |
P13659
|
FINISHED |
| Object | eastbound traffic |
—
|
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: eastbound traffic | Statement: [Bovaird Drive corridor, primaryDirectionServed, eastbound traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDirectionServed Context triple: [Bovaird Drive corridor, primaryDirectionServed, eastbound traffic]
-
A.
primaryCorridorServed
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
B.
servesDirection
Indicates that one entity provides service or functionality oriented toward, or in the direction of, another entity.
-
C.
primaryDirection
chosen
Indicates the main or dominant directional orientation associated with an entity or relation.
-
D.
servedByDirection
Indicates that something (such as a route, service, or facility) is provided or accessed in a specific directional orientation (e.g., northbound, inbound).
-
E.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 22, 2026, 6:43 a.m.