Triple
T10938761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canton of Neuchâtel |
E258406
|
entity |
| Predicate | legislatureSeats |
P96187
|
FINISHED |
| Object | 100 (Grand Council of Neuchâtel) |
—
|
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: 100 (Grand Council of Neuchâtel) | Statement: [Canton of Neuchâtel, legislatureSeats, 100 (Grand Council of Neuchâtel)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislatureSeats Context triple: [Canton of Neuchâtel, legislatureSeats, 100 (Grand Council of Neuchâtel)]
-
A.
legislativeAssemblySeats
Indicates the number of seats an entity holds or is allocated in a legislative assembly.
-
B.
hasLegislativeChamberSeats
Indicates that a legislative chamber holds or is allocated a specified number of seats.
-
C.
parliamentarySeats
Indicates the number of seats a party, group, or representative holds in a parliamentary body.
-
D.
parliamentarySeatsTotal
chosen
Indicates the total number of seats in a given parliament or parliamentary body.
-
E.
legislativeCouncilSeats
Indicates the number of seats held or allocated in a legislative council within a given political or administrative context.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770b12a9881909305db49aa554a1b |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.