Triple

T35446266
Position Surface form Disambiguated ID Type / Status
Subject Do 335 B-1 E1024493 entity
Predicate translationOfNickname P16980 FINISHED
Object Arrow
Arrow is the English nickname for the Dornier Do 335 B-1, a late-World War II German heavy fighter aircraft notable for its unique push-pull twin-engine configuration and exceptional speed.
E1024494 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: Arrow | Statement: [Do 335 B-1, translationOfNickname, Arrow]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Arrow
Triple: [Do 335 B-1, translationOfNickname, Arrow]
Generated description
Arrow is the English nickname for the Dornier Do 335 B-1, a late-World War II German heavy fighter aircraft notable for its unique push-pull twin-engine configuration and exceptional speed.

Provenance (5 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_69f76df8089481909f0018266ee881b7 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79623a6a88190bbd7f3f9e2b33304 completed May 3, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3836c84d00819096d306dd6e45b39e completed June 21, 2026, 7:08 p.m.
NEDg Description generation batch_6a38395a6ae4819086e3d03fecf908f7 completed June 21, 2026, 7:19 p.m.
NED2 Entity disambiguation (via description) batch_6a3839cad16c8190840ed5fc8d72f6b6 completed June 21, 2026, 7:21 p.m.
Created at: May 3, 2026, 4:04 p.m.