Triple
T34683222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Militärstrukturen des Warschauer Paktes |
E890673
|
entity |
| Predicate | dominierendeMacht |
P2547
|
FINISHED |
| Object | Sowjetunion |
—
|
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: Sowjetunion | Statement: [Militärstrukturen des Warschauer Paktes, dominierendeMacht, Sowjetunion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominierendeMacht Context triple: [Militärstrukturen des Warschauer Paktes, dominierendeMacht, Sowjetunion]
-
A.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
B.
imposedDominanceOf
Indicates that one entity has forcibly asserted control, authority, or superiority over another, typically without the latter’s consent.
-
C.
dominantOn
chosen
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
D.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
E.
dominantForm
Indicates that one form, type, or variant is the primary or most prevalent version relative to others in a given context.
- 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_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 2:05 a.m.