Triple
T386993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Johns Bridge |
E8799
|
entity |
| Predicate | hasTrafficType |
P621
|
FINISHED |
| Object | road 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: road traffic | Statement: [St. Johns Bridge, hasTrafficType, road traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrafficType Context triple: [St. Johns Bridge, hasTrafficType, road traffic]
-
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.
trafficType
chosen
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
-
C.
originalTrafficType
Indicates the initial category or source classification of traffic before any changes, redirects, or reattributions occur.
-
D.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
E.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5828d881909e8810061c02480c |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e967d84c8190a6b647f78d95d4e4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.