Triple

T32091578
Position Surface form Disambiguated ID Type / Status
Subject German 243rd Infantry Division E819607 entity
Predicate subunit P35 FINISHED
Object Grenadier Regiment 922
Grenadier Regiment 922 was a German Army infantry regiment of World War II that formed part of the 243rd Infantry Division, serving primarily in defensive operations.
E1994663 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: Grenadier Regiment 922 | Statement: [German 243rd Infantry Division, subunit, Grenadier Regiment 922]
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: Grenadier Regiment 922
Triple: [German 243rd Infantry Division, subunit, Grenadier Regiment 922]
Generated description
Grenadier Regiment 922 was a German Army infantry regiment of World War II that formed part of the 243rd Infantry Division, serving primarily in defensive operations.

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_69f349004b2481908ce2e50af0d579a8 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b63db9dc81908861caf2a676a5d9 completed May 3, 2026, 2:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2f0bbd701481908dbaa5395cfcfd3f completed June 14, 2026, 8:14 p.m.
NEDg Description generation batch_6a2f0cc42ec88190ab1919e86eb481f9 completed June 14, 2026, 8:19 p.m.
NED2 Entity disambiguation (via description) batch_6a2f0d3d950c8190a500acf62470e107 completed June 14, 2026, 8:21 p.m.
Created at: May 1, 2026, 12:25 a.m.