Triple
T31393620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stolbovo |
E800801
|
entity |
| Predicate | relatedConflictOutcome |
P21116
|
FINISHED |
| Object | end of the Ingrian War |
—
|
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: end of the Ingrian War | Statement: [Stolbovo, relatedConflictOutcome, end of the Ingrian War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedConflictOutcome Context triple: [Stolbovo, relatedConflictOutcome, end of the Ingrian War]
-
A.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
B.
conflictResult
chosen
Indicates the outcome or consequence that arises from a particular conflict between entities.
-
C.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
D.
resultOfInternalConflict
Indicates that something occurs or exists as a consequence of an internal conflict within an entity or group.
-
E.
relatedConflictRisk
Indicates a relationship where one entity is associated with, contributes to, or is affected by the risk of conflict involving another 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:19 p.m.