Triple

T33921916
Position Surface form Disambiguated ID Type / Status
Subject Kawasaki Aircraft Industries E869637 entity
Predicate designed P184 FINISHED
Object Kawasaki Ki-102
The Kawasaki Ki-102 was a late-World War II Japanese twin-engine heavy fighter and ground-attack aircraft used by the Imperial Japanese Army Air Service.
E2089753 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: Kawasaki Ki-102 | Statement: [Kawasaki Aircraft Industries, designed, Kawasaki Ki-102]
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: Kawasaki Ki-102
Triple: [Kawasaki Aircraft Industries, designed, Kawasaki Ki-102]
Generated description
The Kawasaki Ki-102 was a late-World War II Japanese twin-engine heavy fighter and ground-attack aircraft used by the Imperial Japanese Army Air Service.

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_69f349992c508190aa4afa24a086cc8c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f701eba5d48190854e10c68a6b4da7 completed May 3, 2026, 8:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36e6066d848190a7dc3dc945d69166 completed June 20, 2026, 7:12 p.m.
NEDg Description generation batch_6a36e89ff0808190a49ce53dc21e3491 completed June 20, 2026, 7:23 p.m.
NED2 Entity disambiguation (via description) batch_6a36e91e81f08190b7ff33ec87865f33 completed June 20, 2026, 7:25 p.m.
Created at: May 1, 2026, 1:49 a.m.