Triple
T29589287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French territorial reform of 2014 |
E754107
|
entity |
| Predicate | didNotChangeStatusOf |
P128186
|
FINISHED |
| Object | Île-de-France region |
—
|
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: Île-de-France region | Statement: [French territorial reform of 2014, didNotChangeStatusOf, Île-de-France region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didNotChangeStatusOf Context triple: [French territorial reform of 2014, didNotChangeStatusOf, Île-de-France region]
-
A.
didNotBecome
Indicates that an expected or potential change of state, role, or condition between entities did not occur.
-
B.
doesNotChange
Indicates that one entity remains unaffected or unaltered by another entity or action.
-
C.
didNotHold
Indicates that an expected event, condition, or relationship failed to occur or be valid.
-
D.
notModifiedBy
chosen
Indicates that an entity has not been altered, changed, or affected by the specified agent or process.
-
E.
notStatus
Indicates that an entity does not have, is not in, or does not match a specified status or 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66db2924881909d004d77dcfd26e7 |
completed | May 2, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:13 p.m.