Triple
T26060424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Armistice with Finland |
E657241
|
entity |
| Predicate | requiredBanOf |
P4355
|
FINISHED |
| Object | fascist organizations in Finland |
—
|
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: fascist organizations in Finland | Statement: [Moscow Armistice with Finland, requiredBanOf, fascist organizations in Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredBanOf Context triple: [Moscow Armistice with Finland, requiredBanOf, fascist organizations in Finland]
-
A.
bannedBy
chosen
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another entity.
-
B.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
C.
reasonForBan
Indicates the justification or cause that led to an entity being banned.
-
D.
requiredExpulsionOf
Indicates that one entity mandates or necessitates the expulsion or removal of another entity.
-
E.
wasBannedAs
Indicates that an entity was prohibited or barred from participation, access, or activity in a specific role, capacity, or status.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 26, 2026, 7:17 p.m.