Triple
T22416047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directive 2009/138/EC |
E554125
|
entity |
| Predicate | celexNumber |
P148083
|
FINISHED |
| Object | 32009L0138 |
—
|
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: 32009L0138 | Statement: [Directive 2009/138/EC, celexNumber, 32009L0138]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celexNumber Context triple: [Directive 2009/138/EC, celexNumber, 32009L0138]
-
A.
annexNumber
Indicates that one entity is identified as an annex or supplementary numbered part associated with another entity.
-
B.
EUAccession
Indicates that an entity becomes a member state of the European Union through the formal accession process.
-
C.
EUAgencyCode
Indicates that an entity is associated with, identified by, or regulated under a specific European Union agency code.
-
D.
conventionNumber
Indicates the identifying number assigned to a specific convention within a series or system of conventions.
-
E.
cantonCode
Indicates the specific administrative canton identifier associated with an entity or location.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.