Triple
T15406847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Käthe Boelcke |
E368480
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Boelcke |
E368479
|
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: Boelcke | Statement: [Käthe Boelcke, familyName, Boelcke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boelcke Context triple: [Käthe Boelcke, familyName, Boelcke]
-
A.
Oswald Boelcke
Oswald Boelcke was a pioneering German World War I fighter ace and tactician, often regarded as one of the founding fathers of air combat doctrine.
-
B.
Jasta Boelcke
Jasta Boelcke was a famed German fighter squadron of the Luftstreitkräfte in World War I, renowned for its high-scoring aces and pioneering air combat tactics.
-
C.
Wilhelm Boelcke
chosen
Wilhelm Boelcke was the father of famed German World War I fighter ace Oswald Boelcke.
-
D.
Kunz von Richthofen
Kunz von Richthofen was a member of the German aristocratic Richthofen family, historically associated with Prussian nobility and military service.
-
E.
Johannes Boelcke
Johannes Boelcke is a descendant of Wilhelm Boelcke, likely known primarily through his connection to this family lineage.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea36c6881909eaea48e9608897a |
completed | April 16, 2026, 1:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c30ae4c8190b7a4739983963e86 |
completed | May 9, 2026, 3:01 p.m. |
Created at: April 10, 2026, 3:20 a.m.