Triple
T30817522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conseil départemental (France) |
E784824
|
entity |
| Predicate | legalNameChangeEffectiveDate |
P801
|
FINISHED |
| Object | 2015-03-22 |
—
|
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: 2015-03-22 | Statement: [Conseil départemental (France), legalNameChangeEffectiveDate, 2015-03-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalNameChangeEffectiveDate Context triple: [Conseil départemental (France), legalNameChangeEffectiveDate, 2015-03-22]
-
A.
nameChangeDate
chosen
Indicates the date on which an entity’s name was officially changed.
-
B.
legalNameChangeBackYear
Indicates the year in which an entity’s legal name was changed back to a previous or original name.
-
C.
administrativeChangeDate
Indicates the date on which an administrative change (such as an update, modification, or reclassification) affecting the entity was officially recorded or took effect.
-
D.
decisionEffectiveDate
Indicates the date on which a particular decision becomes valid, operative, or officially takes effect.
-
E.
lessEffectiveAt
Indicates that one entity has a reduced ability or lower level of success in performing, influencing, or achieving a particular action or outcome compared to another.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 29, 2026, 8:44 p.m.