Triple
T18421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Union |
E363
|
entity |
| Predicate | sideInWorldWarII |
P1427
|
FINISHED |
| Object | Allies |
—
|
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: Allies | Statement: [Soviet Union, sideInWorldWarII, Allies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideInWorldWarII Context triple: [Soviet Union, sideInWorldWarII, Allies]
-
A.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
B.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
C.
navalVesselsAlliedApprox
Indicates that two or more naval vessels are approximately allied, suggesting a cooperative or friendly relationship without specifying a precise or formal alliance.
-
D.
militaryTheater
Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
-
E.
troopStrengthAlliedApprox
Indicates that the approximate troop strength of one entity is being assessed or reported in relation to its allied forces.
- 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_69a240778d288190815c0052ebbbcc91 |
completed | Feb. 28, 2026, 1:10 a.m. |
| NER | Named-entity recognition | batch_69a246cbca108190a92478df126d9bf8 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a2464f61648190ac690044be194972 |
completed | Feb. 28, 2026, 1:35 a.m. |
| PDg | Predicate description generation | batch_69a246cb2904819085c13207565a1db2 |
completed | Feb. 28, 2026, 1:37 a.m. |
Created at: Feb. 28, 2026, 1:14 a.m.