Triple
T5665160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid constituency in the Congress of Deputies |
E124840
|
entity |
| Predicate | isMultiMemberDistrict |
P58846
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Madrid constituency in the Congress of Deputies, isMultiMemberDistrict, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultiMemberDistrict Context triple: [Madrid constituency in the Congress of Deputies, isMultiMemberDistrict, true]
-
A.
usesMultiMemberDistricts
chosen
Indicates that an electoral system or jurisdiction elects multiple representatives from the same district rather than just one.
-
B.
isNonMultiMemberDistrict
Indicates that an electoral district is represented by only a single member rather than multiple members.
-
C.
hasElectoralDistricts
Indicates that a political or administrative unit is divided into one or more electoral districts used for representation or voting.
-
D.
hasCouncilDistrict
Indicates that an entity is located within or represented by a specific council district.
-
E.
hasMembersPerState
Indicates a relationship that specifies how many members are associated with each state.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.