Triple
T34683243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Militärstrukturen des Warschauer Paktes |
E890673
|
entity |
| Predicate | Hauptquartier |
P179765
|
FINISHED |
| Object | Moskau |
—
|
NE NERFINISHED |
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: Moskau | Statement: [Militärstrukturen des Warschauer Paktes, Hauptquartier, Moskau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Hauptquartier Context triple: [Militärstrukturen des Warschauer Paktes, Hauptquartier, Moskau]
-
A.
Befehlskette
Indicates a hierarchical chain of command through which orders or instructions are passed from higher to lower authority levels.
-
B.
حمله
Indicates an aggressive action in which one entity attacks, assaults, or launches an offensive against another.
-
C.
Höhepunkt
Indicates the climax or peak point reached within an event, process, or development.
-
D.
העמיד שושלת
Indicates establishing or founding a lineage or dynasty that continues after the originator.
-
E.
الاستراتيجية
Indicates a strategic relationship in which an entity plans, organizes, or directs actions and resources to achieve specific long-term goals or advantages.
- 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_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727bd39b081908457590c3ba9b745 |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 2:05 a.m.