Triple
T151597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Black Sea Fleet |
E3441
|
entity |
| Predicate | conflictStatus |
P1406
|
FINISHED |
| Object | actively engaged in 2022 Russian invasion of Ukraine |
—
|
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: actively engaged in 2022 Russian invasion of Ukraine | Statement: [Russian Black Sea Fleet, conflictStatus, actively engaged in 2022 Russian invasion of Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictStatus Context triple: [Russian Black Sea Fleet, conflictStatus, actively engaged in 2022 Russian invasion of Ukraine]
-
A.
conflictIn
chosen
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
B.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
C.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
D.
conflictContext
Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
-
E.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580f55a88190b37b54ee0ed5ac7c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.