Triple
T26060422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Armistice with Finland |
E657241
|
entity |
| Predicate | ledToConflict |
P159903
|
FINISHED |
| Object | Lapland War |
—
|
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: Lapland War | Statement: [Moscow Armistice with Finland, ledToConflict, Lapland War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledToConflict Context triple: [Moscow Armistice with Finland, ledToConflict, Lapland War]
-
A.
ledConflict
Indicates that one entity was primarily responsible for initiating, directing, or driving a particular conflict involving another entity or group.
-
B.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
C.
mentionsConflict
Indicates that one entity refers to or discusses a dispute, disagreement, or conflict involving another entity.
-
D.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
E.
wonConflict
Indicates that one entity has prevailed over another in a conflict, contest, or struggle.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60691a4c081909a2589d00b68838d |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:17 p.m.