Triple
T3006495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab 32 Lansen |
E81913
|
entity |
| Predicate | variant |
P4680
|
FINISHED |
| Object | S 32C Lansen |
E319499
|
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: S 32C Lansen | Statement: [Saab 32 Lansen, variant, S 32C Lansen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: S 32C Lansen Context triple: [Saab 32 Lansen, variant, S 32C Lansen]
-
A.
A 32A Lansen
The A 32A Lansen was the ground-attack version of Sweden’s Saab 32 Lansen jet aircraft, optimized for strike missions with enhanced weapons and attack systems.
-
B.
J 32B Lansen
The J 32B Lansen is a Swedish-built, all-weather fighter variant of the Saab 32 Lansen, optimized for air defense and armed with advanced radar and missiles for its time.
-
C.
Lansen
chosen
Lansen is the NATO reporting name for the Swedish Saab 32, a Cold War-era jet aircraft used primarily for attack and reconnaissance roles.
-
D.
Lancer
Lancer is an American Western television series that aired in the late 1960s, following a rancher and his two sons as they defend their California ranch.
-
E.
LC-36A
LC-36A is one of the launch pads at Cape Canaveral’s Launch Complex 36, historically used for Atlas rocket launches.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a48f0888190bdec150dac623851 |
completed | March 8, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1dea3a31481908db6871cf6c37781 |
completed | March 11, 2026, 9:29 p.m. |
Created at: March 8, 2026, 3 p.m.