Triple

T15500384
Position Surface form Disambiguated ID Type / Status
Subject Friedrich von Ingenohl E378934 entity
Predicate appointedAsCommanderOfHighSeasFleet P49361 FINISHED
Object 1913 LITERAL 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: 1913 | Statement: [Friedrich von Ingenohl, appointedAsCommanderOfHighSeasFleet, 1913]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appointedAsCommanderOfHighSeasFleet
Context triple: [Friedrich von Ingenohl, appointedAsCommanderOfHighSeasFleet, 1913]
  • A. appointedChiefOfNavalGeneralStaff
    Indicates that an entity has been formally appointed to the position of Chief of the Naval General Staff for another entity (such as a state, navy, or military organization).
  • B. admiralOfFleet chosen
    Indicates a relationship where a person holds the highest naval rank or command position over an entire fleet.
  • C. notableNavalCommander
    Indicates that the subject is recognized as a distinguished or historically significant commander in naval forces.
  • D. commanderOfLuftwaffe
    Indicates that one entity serves as the commanding officer or leader of the Luftwaffe (the German air force).
  • E. germanCommander
    Indicates that the subject serves as a military commander for German forces in relation to the object.
  • F. None of above.

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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03fcb4e8c81908e4ab463e3ae252b completed April 16, 2026, 1:47 a.m.
PD Predicate disambiguation batch_69ded2896a9c8190a8b9627deb3c17b4 completed April 14, 2026, 11:49 p.m.
Created at: April 10, 2026, 3:54 a.m.