Triple
T9738383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Su-11 |
E236123
|
entity |
| Predicate | successorTo |
P78
|
FINISHED |
| Object | Su-9 |
E234560
|
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: Su-9 | Statement: [Su-11, successorTo, Su-9]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Su-9 Context triple: [Su-11, successorTo, Su-9]
-
A.
Su-9
chosen
The Su-9 was a Soviet supersonic jet interceptor aircraft developed in the 1950s for high-speed, high-altitude air defense missions.
-
B.
Su-11
The Su-11 was a Soviet supersonic interceptor aircraft developed in the early Cold War era to defend Soviet airspace against high-altitude threats.
-
C.
Su-15
The Su-15 was a Soviet supersonic interceptor aircraft developed in the 1960s, best known for its role in Cold War air defense and its involvement in several high-profile shootdown incidents.
-
D.
Su-17
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.
-
E.
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.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef2ba048190811d6f4251fdb270 |
completed | April 1, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc408b988190980db82fbd93e988 |
completed | April 5, 2026, 2:43 a.m. |
Created at: March 30, 2026, 8:22 p.m.