Triple
T10521738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 106(3) TFEU |
E248189
|
entity |
| Predicate | empowersTo |
P33518
|
FINISHED |
| Object | ensure application of Article 106 provisions |
—
|
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: ensure application of Article 106 provisions | Statement: [Article 106(3) TFEU, empowersTo, ensure application of Article 106 provisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: empowersTo Context triple: [Article 106(3) TFEU, empowersTo, ensure application of Article 106 provisions]
-
A.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
B.
believedToGrant
Indicates that something is thought or assumed to provide, confer, or bestow a particular benefit, quality, or effect.
-
C.
grantedPower
Indicates that one entity has conferred authority, control, or a specific capability to another entity.
-
D.
typeOfPowerGranted
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
E.
empoweredBodyTo
chosen
Indicates that one entity has granted another entity the authority, power, or legal capacity to act or make decisions on its behalf.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509dec25881909bc748640f26a416 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:29 p.m.