Triple
T25298932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grosser Stadtrat Luzern |
E634293
|
entity |
| Predicate | hasParliamentaryType |
P6051
|
FINISHED |
| Object | city council |
—
|
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: city council | Statement: [Grosser Stadtrat Luzern, hasParliamentaryType, city council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParliamentaryType Context triple: [Grosser Stadtrat Luzern, hasParliamentaryType, city council]
-
A.
parliamentaryGroupType
Indicates the specific kind or category of parliamentary group to which an entity belongs.
-
B.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
C.
typeOfParliamentaryBody
chosen
Indicates the specific kind or classification of a parliamentary body that an entity represents (e.g., lower house, upper house, unicameral chamber).
-
D.
hasLegislativeType
Indicates that something is associated with, classified by, or characterized as a particular type or category of legislation or legislative measure.
-
E.
hasParliamentaryBodySeatType
Indicates the specific type or category of seat that an entity holds within a parliamentary body.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 1:22 p.m.