Triple

T34788241
Position Surface form Disambiguated ID Type / Status
Subject QF 2-pounder gun E1002870 entity
Predicate mountedOn P3054 FINISHED
Object Cruiser Mk IV tank
The Cruiser Mk IV tank was a British World War II fast cruiser tank, an improved development of earlier cruiser designs, used primarily in the early years of the war.
E2125728 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: Cruiser Mk IV tank | Statement: [QF 2-pounder gun, mountedOn, Cruiser Mk IV tank]
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: Cruiser Mk IV tank
Triple: [QF 2-pounder gun, mountedOn, Cruiser Mk IV tank]
Generated description
The Cruiser Mk IV tank was a British World War II fast cruiser tank, an improved development of earlier cruiser designs, used primarily in the early years of the war.

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_69f76db47d408190a24fc7164439ea2d completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77a604d608190af357dee743ba721 completed May 3, 2026, 4:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37cfcff7248190b1393af06a0dee37 completed June 21, 2026, 11:49 a.m.
NEDg Description generation batch_6a37d07ba708819081b552b8a69313e5 completed June 21, 2026, 11:52 a.m.
NED2 Entity disambiguation (via description) batch_6a37d1935d9881909cee3755fec2d996 completed June 21, 2026, 11:57 a.m.
Created at: May 3, 2026, 3:59 p.m.