Triple
T23892922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | communauté de communes de Parthenay-Gâtine |
E600822
|
entity |
| Predicate | zoneDInfluence |
P2828
|
FINISHED |
| Object | bassin de vie de Parthenay |
—
|
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: bassin de vie de Parthenay | Statement: [communauté de communes de Parthenay-Gâtine, zoneDInfluence, bassin de vie de Parthenay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneDInfluence Context triple: [communauté de communes de Parthenay-Gâtine, zoneDInfluence, bassin de vie de Parthenay]
-
A.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
B.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
-
C.
coreZoneArea
Indicates the area or spatial extent of a designated core zone within a larger region or system.
-
D.
sphereOfInfluence
chosen
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
-
E.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cd050db8819090aa268ba7e5eeed |
completed | April 29, 2026, 9:19 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.