Triple
T27097242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Brigue |
E686338
|
entity |
| Predicate | formerCanton |
P130824
|
FINISHED |
| Object | canton of Tende |
—
|
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: canton of Tende | Statement: [La Brigue, formerCanton, canton of Tende]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCanton Context triple: [La Brigue, formerCanton, canton of Tende]
-
A.
establishedAsCanton
Indicates that an entity was formally created or designated as a canton within an administrative or political system.
-
B.
foundingCantons
Indicates that the referenced entities are the original member regions or states that established or founded a larger political or organizational unit.
-
C.
hasCanton
Indicates that an entity is administratively divided into, or associated with, a specific canton.
-
D.
joinedCanton
chosen
Indicates that an entity became a member of, or was incorporated into, a specific canton.
-
E.
unionInCanton
Indicates that a trade union is located within, operates in, or is jurisdictionally associated with a specific canton.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 27, 2026, 8:45 a.m.