Triple
T27978160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSZ |
E706544
|
entity |
| Predicate | secondaryEnemy |
P180603
|
FINISHED |
| Object | Soviet forces |
—
|
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: Soviet forces | Statement: [NSZ, secondaryEnemy, Soviet forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryEnemy Context triple: [NSZ, secondaryEnemy, Soviet forces]
-
A.
primaryEnemy
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
B.
secondaryOpponent
Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
-
C.
laterEnemyOf
Indicates that one entity becomes an enemy of another at a later time, after not initially being in an antagonistic relationship.
-
D.
secondaryBelligerent
chosen
Indicates that an entity participates in a conflict as a secondary or supporting belligerent rather than as a primary combatant.
-
E.
otherAdversary
Indicates that one entity is an adversary of another, distinct from any primary or previously identified adversary.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 27, 2026, 7:42 p.m.