Triple
T410902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish People’s Army |
E9486
|
entity |
| Predicate | blocAlignment |
P6442
|
FINISHED |
| Object | Eastern Bloc military |
—
|
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: Eastern Bloc military | Statement: [Polish People’s Army, blocAlignment, Eastern Bloc military]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blocAlignment Context triple: [Polish People’s Army, blocAlignment, Eastern Bloc military]
-
A.
alignsWith
chosen
Indicates that one entity is in agreement, harmony, or consistent correspondence with another in terms of position, direction, standard, or principle.
-
B.
primaryAlignment
Indicates the main or most significant way in which one entity is aligned, associated, or in agreement with another entity, standard, or category.
-
C.
aimsToBalance
Indicates an intention or effort by one entity to bring multiple elements, forces, or conditions into a state of equilibrium.
-
D.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
E.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.