Triple
T563179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish–Romanian alliance |
E13496
|
entity |
| Predicate | successorContext |
P16227
|
FINISHED |
| Object | postwar Soviet domination of 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: postwar Soviet domination of Eastern Europe | Statement: [Polish–Romanian alliance, successorContext, postwar Soviet domination of Eastern Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorContext Context triple: [Polish–Romanian alliance, successorContext, postwar Soviet domination of Eastern Europe]
-
A.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
B.
successorProcess
Indicates that one process directly follows another in a defined sequence or workflow.
-
C.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
-
D.
successorOperator
Indicates that one operator directly follows another in a defined sequence or ordering.
-
E.
successorCategory
Indicates that one category directly follows or replaces another in an ordered sequence or hierarchy.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a712bc48190ba298b3c76ab11cc |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a498ff0c0081908947376a38b10d72 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:32 p.m.