Triple
T23892934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | communauté de communes de Parthenay-Gâtine |
E600822
|
entity |
| Predicate | financement |
P154
|
FINISHED |
| Object | fiscalité locale |
—
|
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: fiscalité locale | Statement: [communauté de communes de Parthenay-Gâtine, financement, fiscalité locale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financement Context triple: [communauté de communes de Parthenay-Gâtine, financement, fiscalité locale]
-
A.
fiancee
Indicates that one person is formally engaged to be married to another person.
-
B.
funds
chosen
Indicates that one entity provides financial resources or monetary support to another entity or activity.
-
C.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
-
D.
banking
Indicates that an entity provides or engages in financial services such as holding deposits, managing accounts, or facilitating monetary transactions for another entity.
-
E.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
- 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.