Triple
T4695029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention on the Contract for the International Carriage of Goods by Road |
E104120
|
entity |
| Predicate | protocolDate |
P6878
|
FINISHED |
| Object | 1978-07-05 |
—
|
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: 1978-07-05 | Statement: [Convention on the Contract for the International Carriage of Goods by Road, protocolDate, 1978-07-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protocolDate Context triple: [Convention on the Contract for the International Carriage of Goods by Road, protocolDate, 1978-07-05]
-
A.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
B.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
D.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
-
E.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
- 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.