Triple
T1326806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney Harbour Bridge |
E28345
|
entity |
| Predicate | trafficLanes |
P18336
|
FINISHED |
| Object | 8 road lanes |
—
|
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: 8 road lanes | Statement: [Sydney Harbour Bridge, trafficLanes, 8 road lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficLanes Context triple: [Sydney Harbour Bridge, trafficLanes, 8 road lanes]
-
A.
laneCount
chosen
Indicates the number of parallel lanes associated with a given road or roadway segment.
-
B.
hasLanes
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
C.
hasTrackLanes
Indicates that an entity (such as a road or track) includes one or more designated lanes for vehicle or train movement.
-
D.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
E.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c0a22881909eff0fc6c91a5f41 |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.