Triple
T12505413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NF |
E298934
|
entity |
| Predicate | electoralSystemRole |
P21456
|
FINISHED |
| Object | provided single electoral list for GDR elections |
—
|
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: provided single electoral list for GDR elections | Statement: [NF, electoralSystemRole, provided single electoral list for GDR elections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralSystemRole Context triple: [NF, electoralSystemRole, provided single electoral list for GDR elections]
-
A.
electoralRole
chosen
Indicates the specific function, position, or capacity an entity holds within an electoral process or system.
-
B.
partySystemRole
Indicates the specific functional role or capacity that a party assumes within a given system or context.
-
C.
electsRole
Indicates that one entity selects or votes another entity into a specific role or position.
-
D.
electoralPosition
Indicates that an entity holds, has held, or is a candidate for a specific role or office within an electoral or political system.
-
E.
electoralSystemContext
Indicates the electoral system or framework within which a political or electoral event, action, or relationship takes place.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94dfddf38819099263b8b1e804736 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d43b7008190af2648fe09fd6d23 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:57 p.m.