Triple

T32715518
Position Surface form Disambiguated ID Type / Status
Subject Coat of arms of Nassau E836511 entity
Predicate hasVariant P455 FINISHED
Object arms of Nassau-Siegen
The arms of Nassau-Siegen are a heraldic variant of the Nassau family coat of arms associated specifically with the Nassau-Siegen branch of the noble house.
E2023948 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: arms of Nassau-Siegen | Statement: [Coat of arms of Nassau, hasVariant, arms of Nassau-Siegen]
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: arms of Nassau-Siegen
Triple: [Coat of arms of Nassau, hasVariant, arms of Nassau-Siegen]
Generated description
The arms of Nassau-Siegen are a heraldic variant of the Nassau family coat of arms associated specifically with the Nassau-Siegen branch of the noble house.

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_69f34935455881909088975d79460418 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6c885d48c8190ae96ba6f46fe189a completed May 3, 2026, 4:01 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34b154cef48190864a2561ae9e2bf4 completed June 19, 2026, 3:02 a.m.
NEDg Description generation batch_6a34b2cf98d481909402bb0f9d4b8df7 completed June 19, 2026, 3:09 a.m.
NED2 Entity disambiguation (via description) batch_6a34b379c9688190a5cafed6aecf678a completed June 19, 2026, 3:11 a.m.
Created at: May 1, 2026, 1:11 a.m.