Triple
T3265007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikolai Yudenich |
E68503
|
entity |
| Predicate | afterConflictStatus |
P17908
|
FINISHED |
| Object | exile |
—
|
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: exile | Statement: [Nikolai Yudenich, afterConflictStatus, exile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterConflictStatus Context triple: [Nikolai Yudenich, afterConflictStatus, exile]
-
A.
postConflictStatus
chosen
Indicates the condition or circumstances of an entity after a conflict or dispute has concluded.
-
B.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
C.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another conflict.
-
D.
postConflictContext
Indicates that the relationship or action occurs within, or is shaped by, a setting that follows the end of an armed conflict or violent confrontation.
-
E.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafcb2da08190a7f4fefdfe6d0098 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.