Triple
T30242251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courcouronnes |
E768948
|
entity |
| Predicate | administrativeChangeType |
P38005
|
FINISHED |
| Object | commune merger |
—
|
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: commune merger | Statement: [Courcouronnes, administrativeChangeType, commune merger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeChangeType Context triple: [Courcouronnes, administrativeChangeType, commune merger]
-
A.
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.
-
B.
changeType
chosen
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
C.
alterationType
Indicates the specific kind or category of change or modification that has been applied to an entity or relationship.
-
D.
typeOfAmendment
Indicates the specific kind or category of amendment that is being applied to something, such as a document, law, or agreement.
-
E.
typeOfChangeRegulated
Indicates that one entity specifies or controls the kind of change or modification that is allowed or governed in another entity or process.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 29, 2026, 7:39 p.m.