Triple
T34790461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summa |
E1002929
|
entity |
| Predicate | captureConflict |
P181615
|
FINISHED |
| Object | Winter 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: Winter War | Statement: [Summa, captureConflict, Winter War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captureConflict Context triple: [Summa, captureConflict, Winter War]
-
A.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
B.
wonConflict
Indicates that one entity has prevailed over another in a conflict, contest, or struggle.
-
C.
mentionsConflict
Indicates that one entity refers to or discusses a dispute, disagreement, or conflict involving another entity.
-
D.
subConflict
Indicates that one conflict is a component, phase, or subordinate part of a larger overarching conflict.
-
E.
sawConflict
Indicates that one entity perceived or became aware of a conflict involving another entity or situation.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.