Triple
T34683244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Militärstrukturen des Warschauer Paktes |
E890673
|
entity |
| Predicate | Befehlskette |
P179622
|
FINISHED |
| Object | zentralisiert |
—
|
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: zentralisiert | Statement: [Militärstrukturen des Warschauer Paktes, Befehlskette, zentralisiert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Befehlskette Context triple: [Militärstrukturen des Warschauer Paktes, Befehlskette, zentralisiert]
-
A.
Rechtsfolge
Indicates the legal consequence or effect that follows from a specific legal condition, action, or rule.
-
B.
محاكمة
Indicates that a legal trial or judicial proceeding is being conducted involving the entities.
-
C.
الاستراتيجية
Indicates a strategic relationship in which an entity plans, organizes, or directs actions and resources to achieve specific long-term goals or advantages.
-
D.
Seal of the Hands
Indicates a relationship in which something is formally confirmed, authenticated, or bound through the deliberate action or agreement of specific individuals or parties.
-
E.
Höhepunkt
Indicates the climax or peak point reached within an event, process, or development.
- 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_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. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:05 a.m.