Triple
T3137068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukhoi Su-7 |
E65556
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Sukhoi Su-17 |
E322953
|
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: Sukhoi Su-17 | Statement: [Sukhoi Su-7, successor, Sukhoi Su-17]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sukhoi Su-17 Context triple: [Sukhoi Su-7, successor, Sukhoi Su-17]
-
A.
Su-17
chosen
The Su-17 is a Soviet variable-sweep wing fighter-bomber developed from the Su-7 and widely used for ground-attack and strike missions during the Cold War.
-
B.
Sukhoi Su-7
The Sukhoi Su-7 is a Soviet-era swept-wing fighter-bomber aircraft widely used during the Cold War for ground-attack missions.
-
C.
Su-22
The Su-22 is a Soviet-designed variable-sweep wing fighter-bomber widely exported and used for ground-attack missions by several air forces, including Poland’s.
-
D.
Sukhoi Su-25
The Sukhoi Su-25 is a Soviet-era, twin-engine, subsonic close air support aircraft designed for attacking ground targets in frontline combat.
-
E.
Su-9
The Su-9 was a Soviet supersonic jet interceptor aircraft developed in the 1950s for high-speed, high-altitude air defense 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada564eacc8190a54d07b4eb31c196 |
completed | March 8, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2f3b27a088190b20b3f4404c02c32 |
completed | March 12, 2026, 5:11 p.m. |
Created at: March 8, 2026, 3:05 p.m.