Triple
T27687354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kursk defensive operations |
E698066
|
entity |
| Predicate | opposingOperation |
P52508
|
FINISHED |
| Object | Operation Citadel |
—
|
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: Operation Citadel | Statement: [Kursk defensive operations, opposingOperation, Operation Citadel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingOperation Context triple: [Kursk defensive operations, opposingOperation, Operation Citadel]
-
A.
opposedOperation
chosen
Indicates that one operation is in conflict with, counters, or works against another operation.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
inOperation
Indicates that an entity (such as a system, device, or facility) is currently active, functioning, and performing its intended operation.
-
D.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
E.
opposite
Indicates that one entity is positioned or oriented directly across from, or in a contrary or reverse relation to, 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 2:50 p.m.