Triple
T33468237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cantons of France |
E857113
|
entity |
| Predicate | reorganisationEffectiveFrom |
P44327
|
FINISHED |
| Object | 2015 |
—
|
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 | Statement: [cantons of France, reorganisationEffectiveFrom, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reorganisationEffectiveFrom Context triple: [cantons of France, reorganisationEffectiveFrom, 2015]
-
A.
introducedReorganisationOn
Indicates that an entity initiated or implemented a reorganisation at or on a specific time, date, or occasion.
-
B.
reorganizationYear
chosen
Indicates the year in which an entity underwent a structural or organizational reorganization.
-
C.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
-
D.
furtherReorganizedOn
Indicates that an entity was reorganized again or to a greater extent on a specified later date or occasion.
-
E.
reorganizedAs
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4fb8c808190b0458e3bfe560f05 |
completed | May 3, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.