Triple
T127687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Army |
E2584
|
entity |
| Predicate | roleInHistory |
P4749
|
FINISHED |
| Object | shaped postwar Eastern Europe |
—
|
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: shaped postwar Eastern Europe | Statement: [Red Army, roleInHistory, shaped postwar Eastern Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInHistory Context triple: [Red Army, roleInHistory, shaped postwar Eastern Europe]
-
A.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
B.
historicalImpact
chosen
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
C.
partOfHistoryOf
Indicates that one entity forms a component, episode, or contributing element within the historical development or narrative of another entity.
-
D.
notableCulturalFigure
Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
-
E.
pioneerOf
Indicates that an entity was among the first to develop, introduce, or significantly advance another entity, concept, or practice.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25763ccf8819094e8dffb2ff98480 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564c11208190ad25495609d94d87 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.