Triple
T14292929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fokker 100 |
E354361
|
entity |
| Predicate | manufacturer |
P490
|
FINISHED |
| Object | Fokker |
E387293
|
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: Fokker | Statement: [Fokker 100, manufacturer, Fokker]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fokker Context triple: [Fokker 100, manufacturer, Fokker]
-
A.
Fokker
chosen
Fokker is a historic Dutch aerospace company best known for designing and manufacturing civil and military aircraft.
-
B.
Fokker Universal
The Fokker Universal was a rugged, high-wing monoplane of the 1920s widely used for bush flying, cargo transport, and pioneering commercial aviation in remote regions.
-
C.
Fokker T.VIII
The Fokker T.VIII was a Dutch twin-engined maritime reconnaissance and torpedo bomber seaplane used primarily during the late 1930s and early World War II.
-
D.
Fieseler
Fieseler was a German aircraft manufacturer best known for producing innovative World War II aircraft, including the V-1 flying bomb.
-
E.
Fokker M.5
The Fokker M.5 was an early German monoplane reconnaissance aircraft whose design formed the basis for the famous Fokker Eindecker fighter series of World War I.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de7179368081908117a9ccfbf94fd4 |
completed | April 14, 2026, 4:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3d2281d481909714f8d8cfe71514 |
completed | May 8, 2026, 1:32 a.m. |
Created at: April 10, 2026, 1:11 a.m.