Triple

T20421500
Position Surface form Disambiguated ID Type / Status
Subject German Gymnasium building E500861 entity
Predicate architect P184 FINISHED
Object Edward A. Gruning
Edward A. Gruning was an architect known for designing the German Gymnasium building in London, one of the earliest purpose-built gymnasiums in England.
E2287057 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: Edward A. Gruning | Statement: [German Gymnasium building, architect, Edward A. Gruning]
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: Edward A. Gruning
Triple: [German Gymnasium building, architect, Edward A. Gruning]
Generated description
Edward A. Gruning was an architect known for designing the German Gymnasium building in London, one of the earliest purpose-built gymnasiums in England.

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_69e0b4aa68fc8190b1a14c55575ef04a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67ba479008190bf6d31ee79f3a401 completed April 20, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a475ba1fa548190afbd4e04169f2ef3 completed July 3, 2026, 6:50 a.m.
NEDg Description generation batch_6a475c6b9bac819096e18bf372d7cd0d completed July 3, 2026, 6:53 a.m.
NED2 Entity disambiguation (via description) batch_6a475cb92ecc8190a5e1a5874de4efd0 completed July 3, 2026, 6:54 a.m.
Created at: April 16, 2026, 11:30 a.m.