Triple
T2364050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Cultural Convention |
E47339
|
entity |
| Predicate | conclusionDate |
P140
|
FINISHED |
| Object | 1954-12-19 |
—
|
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: 1954-12-19 | Statement: [European Cultural Convention, conclusionDate, 1954-12-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conclusionDate Context triple: [European Cultural Convention, conclusionDate, 1954-12-19]
-
A.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
B.
concludedSince
Indicates that a particular event, process, or relationship has ended or been brought to a conclusion at some point after a specified reference time.
-
C.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
-
D.
concludedDuring
Indicates that an event, process, or state ended within the temporal bounds of another specified time period or event.
-
E.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc746e7048190a09a38401b367628 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.