Triple
T29118283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Expansion Doctrine |
E737105
|
entity |
| Predicate | keyOpponent |
P13136
|
FINISHED |
| Object | Soviet Red Army |
—
|
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 Red Army | Statement: [Northern Expansion Doctrine, keyOpponent, Soviet Red Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOpponent Context triple: [Northern Expansion Doctrine, keyOpponent, Soviet Red Army]
-
A.
keyOpponents
chosen
Indicates that the subject has primary or most significant opponents identified by the object.
-
B.
keyInternationalOpponent
Indicates that one entity is a primary or significant adversary or rival of another in an international context.
-
C.
recordOpponent
Indicates that one entity is documented or registered as the opposing party or competitor of another entity.
-
D.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
E.
teamOpponent
Indicates that two teams are competing against each other as opponents in a game or match.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661f244fc8190b931f5099dc432d2 |
completed | May 2, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:23 a.m.