Triple
T26057258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canton of Lussac-les-Châteaux |
E657151
|
entity |
| Predicate | hadCommune |
P51099
|
FINISHED |
| Object | Gouex |
—
|
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: Gouex | Statement: [canton of Lussac-les-Châteaux, hadCommune, Gouex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCommune Context triple: [canton of Lussac-les-Châteaux, hadCommune, Gouex]
-
A.
hasCommune
chosen
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
B.
hasCommunesNear
Indicates that one entity has communes located in its nearby geographic vicinity.
-
C.
isUrbanCommuneOf
Indicates that one entity is an urban commune that administratively belongs to or is part of another entity (typically a higher-level territorial unit).
-
D.
hasRuralCommunes
Indicates that an entity possesses, includes, or is associated with one or more rural communes.
-
E.
associatedAutonomousCommunity
Indicates a relationship where an entity is linked or belongs to a specific autonomous community as its relevant regional jurisdiction or affiliation.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 7:12 p.m.