Triple
T2729906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-16 |
E60285
|
entity |
| Predicate | exportVersion |
P18997
|
FINISHED |
| Object | Xian H-6 |
E245753
|
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: Xian H-6 | Statement: [Tupolev Tu-16, exportVersion, Xian H-6]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Xian H-6 Context triple: [Tupolev Tu-16, exportVersion, Xian H-6]
-
A.
Xian H-6
chosen
The Xian H-6 is a Chinese license-built version of the Soviet Tu-16 strategic bomber, extensively modernized and used for long-range strike and maritime attack roles.
-
B.
Ye-6S
Ye-6S was a Soviet spacecraft bus platform used for early lunar orbiters such as Luna 10 during the space race.
-
C.
Y-20
The Y-20 is a large Chinese military transport aircraft designed for strategic airlift of troops, equipment, and supplies over long distances.
-
D.
Shenyang J-16
The Shenyang J-16 is a modern Chinese twin-engine multirole fighter jet derived from the Su-30 design, equipped with advanced avionics and precision strike capabilities.
-
E.
Chengdu J-10
The Chengdu J-10 is a Chinese multirole, single-engine fighter aircraft designed for air superiority and ground attack missions.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaeca6208190a586afb00747146a |
completed | March 7, 2026, 7:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afb69c9f648190bbbcfa42ab68c6f2 |
completed | March 10, 2026, 6:13 a.m. |
Created at: March 6, 2026, 9:56 p.m.