Triple
T12432762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Naval Aviation |
E297071
|
entity |
| Predicate | operates |
P24
|
FINISHED |
| Object | Ka-27 |
E337448
|
NE 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: Ka-27 | Statement: [Russian Naval Aviation, operates, Ka-27]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ka-27 Context triple: [Russian Naval Aviation, operates, Ka-27]
-
A.
Kamov Ka-25
The Kamov Ka-25 is a Soviet-era naval helicopter designed primarily for anti-submarine warfare operations from warships.
-
B.
Kamov Ka-29
The Kamov Ka-29 is a Soviet/Russian shipborne assault and transport helicopter developed from the Ka-27, designed primarily for amphibious assault and troop support operations.
-
C.
Kamov Ka-28 helicopters
chosen
Kamov Ka-28 helicopters are Russian-made, shipborne anti-submarine warfare helicopters widely used for maritime patrol and submarine detection.
-
D.
Mi-8
The Mi-8 is a Soviet-designed twin-turbine transport helicopter widely used around the world for both military and civilian roles.
-
E.
Mi-17
The Mi-17 is a Russian-designed, medium-lift military transport helicopter widely used for troop transport, cargo missions, and search-and-rescue operations.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94d7f2fd08190ab959742dbd8f9c0 |
completed | April 10, 2026, 7:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6349d29c481909a37fd386cc06575 |
completed | May 2, 2026, 5:30 p.m. |
Created at: April 8, 2026, 9:55 p.m.