Triple
T31618647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | СССР |
E806831
|
entity |
| Predicate | участиеВКонфликте |
P167916
|
FINISHED |
| Object | холодная война |
—
|
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: холодная война | Statement: [СССР, участиеВКонфликте, холодная война]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: участиеВКонфликте Context triple: [СССР, участиеВКонфликте, холодная война]
-
A.
conflictParticipantIn
chosen
Indicates that an entity takes part as a participant in a specific conflict or dispute.
-
B.
conflictSide
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
C.
allyInConflict
Indicates that one entity supports and cooperates with another entity as an ally within the context of a specific conflict or dispute.
-
D.
roleInWarOrConflict
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
E.
warParticipatedIn
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:40 p.m.