Triple
T27142807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Parliament constituencies in Ireland |
E681858
|
entity |
| Predicate | changedDueTo |
P5019
|
FINISHED |
| Object | EU enlargement |
—
|
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: EU enlargement | Statement: [European Parliament constituencies in Ireland, changedDueTo, EU enlargement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedDueTo Context triple: [European Parliament constituencies in Ireland, changedDueTo, EU enlargement]
-
A.
changedAfter
Indicates that one entity underwent a change at a point in time that is later than the time at which another referenced entity changed.
-
B.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
C.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
-
D.
changedOn
Indicates that an entity underwent a modification or update at a specific point in time.
-
E.
changeReason
chosen
Indicates the reason or justification for a modification or change made to an entity or its state.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f624c2ed0c819091dde69fc6084d4a |
completed | May 2, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:10 a.m.