Triple
T38343932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebbeke |
E1041484
|
entity |
| Predicate | hasMunicipalCouncilParty |
P198334
|
FINISHED |
| Object | N-VA |
—
|
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: N-VA | Statement: [Lebbeke, hasMunicipalCouncilParty, N-VA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalCouncilParty Context triple: [Lebbeke, hasMunicipalCouncilParty, N-VA]
-
A.
hasMunicipalCouncilType
Indicates the specific form or structure of municipal council governance that an administrative unit uses.
-
B.
hasMunicipalCouncilTerm
Indicates that a municipal council serves or holds office during a specified term or period.
-
C.
hasMunicipalCouncilUntil
Indicates that a municipal council served as the governing body of an entity up to a specified end date or point in time.
-
D.
hasLocalPartyCommittee
Indicates that an entity has an associated party committee operating at the local or regional level.
-
E.
hasMunicipalExecutiveCommittee
Indicates that a municipality is associated with a specific executive committee responsible for its administrative or executive functions.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
| PDg | Predicate description generation | batch_69fedd5915588190bd884054e4be0414 |
completed | May 9, 2026, 7:08 a.m. |
Created at: May 3, 2026, 4:30 p.m.