Triple
T11500747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penang Bridge |
E272656
|
entity |
| Predicate | hasLaneDirection |
P39910
|
FINISHED |
| Object | three lanes each direction |
—
|
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: three lanes each direction | Statement: [Penang Bridge, hasLaneDirection, three lanes each direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaneDirection Context triple: [Penang Bridge, hasLaneDirection, three lanes each direction]
-
A.
hasLanes
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
B.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
C.
hasLaneConfigurations
chosen
Indicates that an entity is associated with one or more specific arrangements or patterns of lanes (e.g., number, type, or direction of lanes).
-
D.
hasDedicatedLanes
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
-
E.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de3e9c881909d6c55334f7a832d |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.