Triple
T33513081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dublin system |
E858297
|
entity |
| Predicate | reformDiscussedBy |
P48027
|
FINISHED |
| Object | European Commission |
—
|
NE NERFINISHED |
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: European Commission | Statement: [Dublin system, reformDiscussedBy, European Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformDiscussedBy Context triple: [Dublin system, reformDiscussedBy, European Commission]
-
A.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
B.
subjectToReformBy
chosen
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
-
C.
advocatedReformOf
Indicates that one entity publicly supported or promoted changes to another entity, typically aiming to improve or modify its structure, policies, or practices.
-
D.
relatedReforms
Indicates that one reform is connected or associated with another reform, typically through shared goals, content, or impact.
-
E.
reformsBy
Indicates that one entity initiates, implements, or is responsible for changes or improvements (reforms) affecting another 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.