Triple
T13821964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Directive 92/43/EEC |
E332158
|
entity |
| Predicate | includesAnnex |
P78069
|
FINISHED |
| Object | Annex I |
—
|
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: Annex I | Statement: [Council Directive 92/43/EEC, includesAnnex, Annex I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAnnex Context triple: [Council Directive 92/43/EEC, includesAnnex, Annex I]
-
A.
annex
Indicates the act of formally incorporating one entity, typically a territory, into the domain or control of another.
-
B.
annexedBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
-
C.
annexes
Indicates that one entity formally incorporates another entity or territory into its own domain, typically extending its control or sovereignty over it.
-
D.
hasAppendix
chosen
Indicates that one entity includes or is associated with an appendix section related to another entity.
-
E.
annexCount
Indicates the number of annexes or supplementary parts associated with a primary entity or document.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0284428081908043c55caeefb833 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.