Triple
T34683266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Militärstrukturen des Warschauer Paktes |
E890673
|
entity |
| Predicate | EndeDurch |
P3587
|
FINISHED |
| Object | politischer Umbruch in Osteuropa 1989–1991 |
—
|
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: politischer Umbruch in Osteuropa 1989–1991 | Statement: [Militärstrukturen des Warschauer Paktes, EndeDurch, politischer Umbruch in Osteuropa 1989–1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EndeDurch Context triple: [Militärstrukturen des Warschauer Paktes, EndeDurch, politischer Umbruch in Osteuropa 1989–1991]
-
A.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
B.
eraEnd
Indicates the point in time or event at which a particular era, period, or phase comes to a close.
-
C.
endedWith
chosen
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
D.
endName
Indicates that one entity serves as the ending or final name/designation associated with another entity.
-
E.
نوع النهاية
Indicates the type or nature of an ending or conclusion associated with an entity or event.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7232a16a081909b775efc60b45244 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.