Triple
T1738556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnegie, Angus |
E37975
|
entity |
| Predicate | roadAccessCountryStandard |
P7767
|
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: [Carnegie, Angus, roadAccessCountryStandard, left-hand traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadAccessCountryStandard Context triple: [Carnegie, Angus, roadAccessCountryStandard, left-hand traffic]
-
A.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
-
B.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
C.
roadTrafficRuleJurisdiction
chosen
Indicates the jurisdiction or authority under whose road traffic rules a given situation, entity, or action is governed.
-
D.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
E.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.