Triple
T31329029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General council of France |
E798973
|
entity |
| Predicate | successorBodyNameChange |
P3901
|
FINISHED |
| Object | Departmental council |
—
|
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: Departmental council | Statement: [General council of France, successorBodyNameChange, Departmental council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorBodyNameChange Context triple: [General council of France, successorBodyNameChange, Departmental council]
-
A.
successorNameChange
Indicates that an entity’s name has been changed to a new name that succeeds or replaces its previous name.
-
B.
successorBody
chosen
Indicates that one body or entity directly follows and replaces another in a sequence or succession.
-
C.
successorNameForm
Indicates that the object is the name or naming form used for the successor entity that follows the subject in a sequence or lineage.
-
D.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
-
E.
successorBodyStyleChange
Indicates that one body style directly follows and replaces another in a sequence of design or model changes.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: April 29, 2026, 9:16 p.m.