Triple
T22416046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directive 2009/138/EC |
E554125
|
entity |
| Predicate | datePublishedInOfficialJournal |
P60314
|
FINISHED |
| Object | 2009-12-17 |
—
|
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: 2009-12-17 | Statement: [Directive 2009/138/EC, datePublishedInOfficialJournal, 2009-12-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datePublishedInOfficialJournal Context triple: [Directive 2009/138/EC, datePublishedInOfficialJournal, 2009-12-17]
-
A.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
-
B.
OJPublicationDate
chosen
Indicates the date on which something is officially published in the Official Journal.
-
C.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
D.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
E.
fullPublicationDate
Indicates the complete calendar date on which something is formally published, including day, month, and year.
- 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1594615f881909688b02548ee83eb |
completed | April 29, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.