Triple
T28447663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andenne |
E715885
|
entity |
| Predicate | hasMunicipalCouncilSize |
P2433
|
FINISHED |
| Object | 29 |
—
|
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: 29 | Statement: [Andenne, hasMunicipalCouncilSize, 29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalCouncilSize Context triple: [Andenne, hasMunicipalCouncilSize, 29]
-
A.
hasMunicipalCouncilType
Indicates the specific form or structure of municipal council governance that an administrative unit uses.
-
B.
hasMunicipalCouncilUntil
Indicates that a municipal council served as the governing body of an entity up to a specified end date or point in time.
-
C.
hasNumberOfCouncillors
chosen
Indicates the relationship that specifies how many councillors are associated with a given entity.
-
D.
usedToHaveMunicipalCouncil
Indicates that an entity previously had, but no longer has, a municipal council as its local governing body.
-
E.
hasMunicipalWards
Indicates that a municipality is divided into and associated with one or more municipal wards as its internal administrative units.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 1:50 a.m.