Triple
T2623543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDGB |
E59063
|
entity |
| Predicate | hadRightToNominate |
P1791
|
FINISHED |
| Object | candidates for the Volkskammer |
—
|
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: candidates for the Volkskammer | Statement: [FDGB, hadRightToNominate, candidates for the Volkskammer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRightToNominate Context triple: [FDGB, hadRightToNominate, candidates for the Volkskammer]
-
A.
candidateNomination
Indicates that an individual is formally put forward or proposed as a candidate for a position, role, or office.
-
B.
nominated
chosen
Indicates that one entity formally proposes or selects another entity for a position, role, award, or recognition.
-
C.
nominationOutcome
Indicates the result or status that a nomination process yields for a candidate or entity.
-
D.
wasCandidateIn
Indicates that an entity served as a candidate in a particular election, contest, or selection process.
-
E.
couldElect
Indicates that one entity has the potential or ability, under certain conditions or rules, to choose another entity for an office, role, or position through an election.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.