Triple
T3985113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab 2000 |
E86851
|
entity |
| Predicate | manufacturer |
P490
|
FINISHED |
| Object | Saab Aircraft |
E15976
|
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: Saab Aircraft | Statement: [Saab 2000, manufacturer, Saab Aircraft]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saab Aircraft Context triple: [Saab 2000, manufacturer, Saab Aircraft]
-
A.
Saab AB
chosen
Saab AB is a Swedish aerospace and defense company known for developing military aircraft, advanced defense systems, and security solutions.
-
B.
Saab Automobile
Saab Automobile was a Swedish car manufacturer known for its innovative engineering, turbocharged engines, and distinctive, safety-focused designs.
-
C.
Saab Kockums
Saab Kockums is a Swedish shipyard and defense company best known for designing and building advanced submarines and naval vessels.
-
D.
Saab 2000
The Saab 2000 is a high-speed twin‑engine turboprop regional airliner developed in the 1990s, known for its fast cruise performance and efficient short- to medium-haul operations.
-
E.
Saab 340
The Saab 340 is a twin‑engine turboprop regional airliner widely used for short-haul passenger services around the world.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef9dfaf28819081b547836d79b889 |
completed | March 9, 2026, 4:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5a831b0408190a0862803844d779d |
completed | March 14, 2026, 6:25 p.m. |
Created at: March 9, 2026, 3:33 p.m.