Triple
T4976147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fokker Dr.I |
E111769
|
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 Dr.I, manufacturer, Fokker]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fokker Context triple: [Fokker Dr.I, 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.
Fieseler
Fieseler was a German aircraft manufacturer best known for producing innovative World War II aircraft, including the V-1 flying bomb.
-
D.
Fokker Dr.I
The Fokker Dr.I was a famous German World War I triplane fighter, best known as the aircraft flown by the Red Baron, Manfred von Richthofen.
-
E.
Junkers
Junkers was a pioneering German aircraft manufacturer renowned for producing innovative military and civilian airplanes, particularly during the early to mid-20th century.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7230086c81909c045614721bd89f |
completed | March 20, 2026, 4:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be8a0634b48190acb4a1834f5647cf |
completed | March 21, 2026, 12:07 p.m. |
Created at: March 20, 2026, 1:33 p.m.