Triple
T11208834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swift PR.6 |
E265248
|
entity |
| Predicate | developedFrom |
P1245
|
FINISHED |
| Object | Swift F.4 |
E273358
|
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: Swift F.4 | Statement: [Swift PR.6, developedFrom, Swift F.4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Swift F.4 Context triple: [Swift PR.6, developedFrom, Swift F.4]
-
A.
Swift F.4
chosen
The Swift F.4 was a later, improved fighter variant of the British Supermarine Swift jet, featuring enhanced performance and handling over earlier models.
-
B.
Swift F.2
The Swift F.2 was an early production fighter variant of the British Supermarine Swift jet, featuring improved armament and performance over the initial models.
-
C.
Swift F.1
The Swift F.1 was an early production variant of the British Supermarine Swift jet fighter, used briefly by the Royal Air Force in the 1950s.
-
D.
Swift F.3
The Swift F.3 was a later, improved variant of the British Supermarine Swift jet fighter, featuring upgraded performance and systems over its predecessors.
-
E.
Meteor F.4
The Meteor F.4 was an early post-World War II British jet fighter variant of the Gloster Meteor, featuring improved engines and performance over its predecessors.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d5f8908190903817f84c629ba1 |
completed | April 9, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4cc2ec5348190b66a3cc5779aa327 |
completed | April 19, 2026, 12:35 p.m. |
Created at: April 8, 2026, 9:30 p.m.