Triple
T4622137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auckland Harbour Bridge |
E101009
|
entity |
| Predicate | laneManagement |
P18246
|
FINISHED |
| Object | tidal flow system |
—
|
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: tidal flow system | Statement: [Auckland Harbour Bridge, laneManagement, tidal flow system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laneManagement Context triple: [Auckland Harbour Bridge, laneManagement, tidal flow system]
-
A.
trafficManagementStrategy
Indicates a method or plan used to control, organize, or optimize the flow of traffic within a transportation system.
-
B.
facilitatesTrafficFlowBetween
Indicates that one entity enables, supports, or improves the movement of traffic between two other entities or locations.
-
C.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
D.
hasTrafficManagement
chosen
Indicates that an entity implements, uses, or is associated with systems or measures for controlling and optimizing traffic flow.
-
E.
laneCount
Indicates the number of parallel lanes associated with a given road or roadway segment.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a0374308190aeaffc9d866a3742 |
completed | March 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.