Triple
T32546811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Directive 79/409/EEC |
E831867
|
entity |
| Predicate | EECDirectiveNumber |
P174580
|
FINISHED |
| Object | 79/409/EEC |
—
|
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: 79/409/EEC | Statement: [Council Directive 79/409/EEC, EECDirectiveNumber, 79/409/EEC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EECDirectiveNumber Context triple: [Council Directive 79/409/EEC, EECDirectiveNumber, 79/409/EEC]
-
A.
EIPNumber
Indicates that an entity is associated with a specific Ethereum Improvement Proposal (EIP) identifier number.
-
B.
guidelineNumber
Indicates the specific numeric identifier assigned to a guideline within a set of rules, standards, or recommendations.
-
C.
celexNumber
Indicates the official CELEX identifier assigned to a legal act or document within the EU legal database.
-
D.
FCC-ee
Indicates a relationship or context involving the FCC-ee particle collider project, such as participation in, association with, or relevance to that experimental facility.
-
E.
circuitDirection
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5bfe55881909a20ef79180d19c4 |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:02 a.m.