Triple
T18967066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention on Road Traffic (1949) |
E464067
|
entity |
| Predicate | articleSubject |
P450
|
FINISHED |
| Object | driver obligations |
—
|
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: driver obligations | Statement: [Convention on Road Traffic (1949), articleSubject, driver obligations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: articleSubject Context triple: [Convention on Road Traffic (1949), articleSubject, driver obligations]
-
A.
articleIISubject
Indicates that the entity functions as the grammatical subject of a sentence governed by Article II.
-
B.
subjectMatter
chosen
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
C.
articleType
Indicates the specific category or kind of article associated with an entity.
-
D.
articleContent
Indicates that one entity is the textual or media content that makes up the body of another entity, typically an article or document.
-
E.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d7183c8190b1258c0381233efd |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon