Triple
T4694859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention on Road Traffic (1968) |
E104117
|
entity |
| Predicate | articleCovers |
P34767
|
FINISHED |
| Object | rules of the road |
—
|
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: rules of the road | Statement: [Convention on Road Traffic (1968), articleCovers, rules of the road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: articleCovers Context triple: [Convention on Road Traffic (1968), articleCovers, rules of the road]
-
A.
articleType
Indicates the specific category or kind of article associated with an entity.
-
B.
articleContent
chosen
Indicates that one entity is the textual or media content that makes up the body of another entity, typically an article or document.
-
C.
article2Content
Indicates that one article serves as the content or body text for another article or higher-level publication entity.
-
D.
containsArticle
Indicates that one entity includes or holds an article (such as a written piece, item, or document) as part of its contents.
-
E.
article9FocusesOn
Indicates that the subject (e.g., a document or discussion) primarily concerns or centers on the topic specified as Article 9.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.