Triple

T34767156
Position Surface form Disambiguated ID Type / Status
Subject Fanny Elssler E1002249 entity
Predicate father P120 FINISHED
Object Johann Florian Elssler
Johann Florian Elssler was an Austrian copyist and archivist at the Vienna Court Opera, best known as the father of the celebrated Romantic-era ballerina Fanny Elssler.
E2111731 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: Johann Florian Elssler | Statement: [Fanny Elssler, father, Johann Florian Elssler]
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: Johann Florian Elssler
Triple: [Fanny Elssler, father, Johann Florian Elssler]
Generated description
Johann Florian Elssler was an Austrian copyist and archivist at the Vienna Court Opera, best known as the father of the celebrated Romantic-era ballerina Fanny Elssler.

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_69f76db20dac8190b1e8d0ca4dc1d59f completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77a1f24648190be078d25376e6483 completed May 3, 2026, 4:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a376637bf7881909af58a5f6bf19546 completed June 21, 2026, 4:19 a.m.
NEDg Description generation batch_6a37676603f48190b96647fd932da6e3 completed June 21, 2026, 4:24 a.m.
NED2 Entity disambiguation (via description) batch_6a3767ee52ec8190bae0b73d8f572af1 completed June 21, 2026, 4:26 a.m.
Created at: May 3, 2026, 3:59 p.m.