Triple
T22809826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | October 1949 East German general election |
E564641
|
entity |
| Predicate | multiPartyCompetition |
P149805
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [October 1949 East German general election, multiPartyCompetition, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiPartyCompetition Context triple: [October 1949 East German general election, multiPartyCompetition, no]
-
A.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
C.
competeIn
Indicates that an entity takes part as a contender in a particular event, activity, or domain where performance is compared against others.
-
D.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
E.
competencia
Indicates that one entity is in a state of competition or rivalry with another, typically striving to achieve a similar goal or advantage.
- F. None of above. chosen
Provenance (4 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5f1f348190a35e87939732c99f |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:32 p.m.