Triple

T37296843
Position Surface form Disambiguated ID Type / Status
Subject United States Navy Band E925827 entity
Predicate hasUnit P35 FINISHED
Object Ceremonial Band
The Ceremonial Band is a specialized ensemble within the United States Navy Band that performs at official military ceremonies, state functions, and public patriotic events.
E2221401 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: Ceremonial Band | Statement: [United States Navy Band, hasUnit, Ceremonial Band]
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: Ceremonial Band
Triple: [United States Navy Band, hasUnit, Ceremonial Band]
Generated description
The Ceremonial Band is a specialized ensemble within the United States Navy Band that performs at official military ceremonies, state functions, and public patriotic events.

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_69f76eb0f86c819098dee07393e69ec3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb5aec70a081909b5badcb0c98a527 completed May 6, 2026, 3:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40514989488190873d45fbb36f819c completed June 27, 2026, 10:40 p.m.
NEDg Description generation batch_6a4052740ba08190aadef914c8fc996d completed June 27, 2026, 10:45 p.m.
NED2 Entity disambiguation (via description) batch_6a4057ce44a8819099cd8d1e99077184 completed June 27, 2026, 11:07 p.m.
Created at: May 3, 2026, 4:16 p.m.