Triple

T34732388
Position Surface form Disambiguated ID Type / Status
Subject Großer Saal E1001246 entity
Predicate translationOfName P15 FINISHED
Object Great Hall
The Great Hall is a large, often grand ceremonial or assembly space commonly found in castles, universities, and public buildings, used for gatherings, banquets, and important events.
E694717 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: Great Hall | Statement: [Großer Saal, translationOfName, Great Hall]
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: Great Hall
Triple: [Großer Saal, translationOfName, Great Hall]
Generated description
The Great Hall is a large, often grand ceremonial or assembly space commonly found in castles, universities, and public buildings, used for gatherings, banquets, and important 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_69f76daf739881909ed3554f98a2b433 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f779ae53c08190b2675e527e5e303a completed May 3, 2026, 4:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a376626c5f4819099d509dd203b7564 completed June 21, 2026, 4:18 a.m.
NEDg Description generation batch_6a376a26b25881908e64caa8567d57c6 completed June 21, 2026, 4:35 a.m.
NED2 Entity disambiguation (via description) batch_6a376a7fccc88190ba75271b8fc7dd2d completed June 21, 2026, 4:37 a.m.
Created at: May 3, 2026, 3:59 p.m.