Triple
T35667464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patroon Island Bridge |
E1030611
|
entity |
| Predicate | carriesTrafficDirection |
P3915
|
FINISHED |
| Object | eastbound |
—
|
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 | Statement: [Patroon Island Bridge, carriesTrafficDirection, eastbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriesTrafficDirection Context triple: [Patroon Island Bridge, carriesTrafficDirection, eastbound]
-
A.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
B.
trafficDirection
chosen
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
C.
crossingDirection
Indicates the direction in which one entity moves or passes across another reference point, boundary, or path.
-
D.
facilitatesTrafficTowards
Indicates that one entity enables, promotes, or directs the movement or flow of traffic toward another entity.
-
E.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fae59588190bf0de193783c5de2 |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.