Triple
T5175861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Sea Fleet Air Force |
E116795
|
entity |
| Predicate | primaryEnemyTheater |
P710
|
FINISHED |
| Object | Axis forces in Black Sea |
—
|
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: Axis forces in Black Sea | Statement: [Black Sea Fleet Air Force, primaryEnemyTheater, Axis forces in Black Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEnemyTheater Context triple: [Black Sea Fleet Air Force, primaryEnemyTheater, Axis forces in Black Sea]
-
A.
primaryEnemyForces
Indicates that the related entities constitute the main opposing or hostile forces in a conflict or competitive situation.
-
B.
primaryEnemy
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
C.
regionOfConflict
Indicates that a specified region is the location where a particular conflict or dispute takes place.
-
D.
militaryTheater
chosen
Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
-
E.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd797349008190b87ad9d0d3eb667f |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.