Triple
T23892907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | communauté de communes de Parthenay-Gâtine |
E600822
|
entity |
| Predicate | regroupeAutourDe |
P115046
|
FINISHED |
| Object | 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: Parthenay | Statement: [communauté de communes de Parthenay-Gâtine, regroupeAutourDe, Parthenay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regroupeAutourDe Context triple: [communauté de communes de Parthenay-Gâtine, regroupeAutourDe, Parthenay]
-
A.
seDérouleAutourDe
Indicates that an event or process takes place around, centers on, or is organized about a particular entity or theme.
-
B.
allyGroup
Indicates that two or more entities belong to the same allied group or faction, cooperating or aligned in purpose or interests.
-
C.
organizedAround
Indicates that something is structured, arranged, or centered with respect to a particular focus, principle, or organizing element.
-
D.
groupTogether
chosen
Indicates that multiple entities are treated or arranged as a single collective unit or set.
-
E.
movementGrouping
Indicates that multiple movements or motion events are treated as a single grouped or coordinated unit within a larger action or process.
- 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.