Triple
T32841803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adamstown, Pitcairn Islands |
E839989
|
entity |
| Predicate | vehicleTrafficSide |
P4069
|
FINISHED |
| Object | left |
—
|
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: left | Statement: [Adamstown, Pitcairn Islands, vehicleTrafficSide, left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleTrafficSide Context triple: [Adamstown, Pitcairn Islands, vehicleTrafficSide, left]
-
A.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
B.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
C.
hasTrafficDirection
chosen
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
D.
routesTrafficThrough
Indicates that network traffic originating from one entity is directed to pass through another entity as an intermediate path or conduit.
-
E.
cargoTrafficRank
Indicates the relative position of an entity in an ordered list based on the volume or intensity of its cargo traffic.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:16 a.m.