Triple
T10456849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai–Lao Friendship Bridge |
E246571
|
entity |
| Predicate | trafficDirectionOnBridge |
P3915
|
FINISHED |
| Object | left-hand 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: left-hand traffic | Statement: [Thai–Lao Friendship Bridge, trafficDirectionOnBridge, left-hand traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficDirectionOnBridge Context triple: [Thai–Lao Friendship Bridge, trafficDirectionOnBridge, left-hand traffic]
-
A.
trafficDirection
chosen
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
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
D.
riverCrossedByMaintainedBridges
Indicates that a river is spanned by one or more bridges that are actively maintained in usable condition.
-
E.
touristTraffic
Indicates the level, flow, or intensity of tourists visiting or moving through a particular place or area.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe498a808190b88530f0221df4a6 |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:18 p.m.