Triple
T871314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union financial regulators |
E18818
|
entity |
| Predicate | implement |
P2539
|
FINISHED |
| Object | EU financial directives |
—
|
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: EU financial directives | Statement: [European Union financial regulators, implement, EU financial directives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implement Context triple: [European Union financial regulators, implement, EU financial directives]
-
A.
implementedThrough
Indicates that something is realized, carried out, or made operational by means of a specified method, mechanism, or intermediary.
-
B.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
C.
aimedToImplement
Indicates that an entity had the intention or plan to carry out, realize, or put another entity (such as a policy, idea, or system) into effect.
-
D.
implementedUnder
chosen
Indicates that an action, policy, or process is carried out within the scope, authority, or framework defined by a particular higher-level plan, rule, or governing entity.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac94d5ac81909feee876696da589 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.