Triple
T16384454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stalin’s organ |
E397884
|
entity |
| Predicate | opponentsWhoUsedName |
P91463
|
FINISHED |
| Object | German soldiers |
—
|
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: German soldiers | Statement: [Stalin’s organ, opponentsWhoUsedName, German soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentsWhoUsedName Context triple: [Stalin’s organ, opponentsWhoUsedName, German soldiers]
-
A.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
-
B.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
C.
consideredOpponentsAs
Indicates that one entity regarded or treated another entity as an opponent or adversary.
-
D.
allegedByOpponents
Indicates that a claim or accusation is made by opponents of the subject.
-
E.
codenameByOpponents
chosen
Indicates that opponents assign or use a particular codename for the referenced entity.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319de83248190b5d43646fa9b6cda |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.