Triple

T20059739
Position Surface form Disambiguated ID Type / Status
Subject Argus As 10 E499435 entity
Predicate application P98 FINISHED
Object Arado Ar 96 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: Arado Ar 96 | Statement: [Argus As 10, application, Arado Ar 96]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arado Ar 96
Context triple: [Argus As 10, application, Arado Ar 96]
  • A. Arado Ar 96 chosen
    The Arado Ar 96 was a German single-engine advanced trainer aircraft widely used by the Luftwaffe during World War II for pilot instruction and transition training.
  • B. Arado Ar 95
    The Arado Ar 95 was a German two-seat reconnaissance and patrol floatplane developed in the late 1930s for use by the Kriegsmarine.
  • C. Arado Ar 66
    The Arado Ar 66 was a German biplane trainer aircraft used extensively by the Luftwaffe in the 1930s and during the early years of World War II.
  • D. Arado Ar 67
    The Arado Ar 67 was a German single-seat biplane fighter prototype developed in the 1930s that did not enter mass production.
  • E. Arado Ar 65
    The Arado Ar 65 was a German single-seat biplane fighter aircraft of the early 1930s used by the nascent Luftwaffe as one of its first standard fighters.
  • 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_69da6276bcf48190aabbf279192a5fb4 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66374f4a48190beb575a6c84ebdb4 completed April 20, 2026, 5:33 p.m.
Created at: April 11, 2026, 3:38 p.m.