Triple

T23294117
Position Surface form Disambiguated ID Type / Status
Subject Fokker C.XI-W E590115 entity
Predicate manufacturer P490 FINISHED
Object Fokker NE NERFINISHED

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 C.XI-W, manufacturer, Fokker]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fokker
Context triple: [Fokker C.XI-W, 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 (2 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_69e25d1af9d88190a0b9b5e8fa608618 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f196cdce7081908ca1cf9107b87f61 completed April 29, 2026, 5:27 a.m.
Created at: April 17, 2026, 5:02 p.m.