Triple

T36935973
Position Surface form Disambiguated ID Type / Status
Subject Omaha Knights E913619 entity
Predicate homeArena P373 FINISHED
Object Omaha Auditorium
Omaha Auditorium was a multi-purpose indoor arena in Omaha, Nebraska, historically known for hosting ice hockey teams such as the Omaha Knights as well as various sports and entertainment events.
E851423 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: Omaha Auditorium | Statement: [Omaha Knights, homeArena, Omaha Auditorium]
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: Omaha Auditorium
Triple: [Omaha Knights, homeArena, Omaha Auditorium]
Generated description
Omaha Auditorium was a multi-purpose indoor arena in Omaha, Nebraska, historically known for hosting ice hockey teams such as the Omaha Knights as well as various sports and entertainment 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_69f76e8a6a5c81909c1febf32bf3fe23 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f9fdf5cccc81909f55ca78c6591790 completed May 5, 2026, 2:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3e5750a3d08190b7077f0b3c79034a completed June 26, 2026, 10:41 a.m.
NEDg Description generation batch_6a3e5861b2b48190b5958130724324d1 completed June 26, 2026, 10:45 a.m.
NED2 Entity disambiguation (via description) batch_6a3e5f7deea0819096307262cf2134a4 completed June 26, 2026, 11:16 a.m.
Created at: May 3, 2026, 4:13 p.m.