Triple
T29382598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Decisions |
E745173
|
entity |
| Predicate | providedForIn |
P191893
|
FINISHED |
| Object | Article 288 TFEU |
—
|
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: Article 288 TFEU | Statement: [Council Decisions, providedForIn, Article 288 TFEU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedForIn Context triple: [Council Decisions, providedForIn, Article 288 TFEU]
-
A.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
B.
providedForExtension
Indicates that something is supplied or made available specifically to support or enable an extension of another thing (such as functionality, duration, or scope).
-
C.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
D.
mayProvideFor
Indicates that one entity is permitted or has the option to supply, support, or otherwise furnish something for another entity.
-
E.
meetsInPresenceOf
Indicates that two or more entities meet or interact while another specified entity is present as a witness, chaperone, or contextual participant.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69fcef636dfc819085cf91323f2e4edd |
completed | May 7, 2026, 8 p.m. |
Created at: April 28, 2026, 2:36 p.m.