Triple
T26307827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipal council of Decize |
E661736
|
entity |
| Predicate | locatedInCentralFrance |
P193989
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [municipal council of Decize, locatedInCentralFrance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCentralFrance Context triple: [municipal council of Decize, locatedInCentralFrance, true]
-
A.
locatedInMetropolitanFrance
Indicates that the subject is geographically situated within the territory of metropolitan (continental) France.
-
B.
situéeDansLeDépartement
Indicates that one entity is located within the administrative boundaries of a specific department.
-
C.
locatedInCentralEurope
Indicates that something is geographically situated within the region of Central Europe.
-
D.
mainIntermediateNodeFrance
Indicates that an entity serves as the primary intermediate node or transit point within or related to France in a given network or process.
-
E.
primaryFrenchDestination
Indicates that one entity is the main or most significant travel destination in France for another entity.
- F. None of above. chosen
Provenance (4 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: April 26, 2026, 10:20 p.m.