Triple

T33647202
Position Surface form Disambiguated ID Type / Status
Subject Medieval Lives of Saint George E861990 entity
Predicate setting P1957 FINISHED
Object city of Silene
The city of Silene is a legendary locale in Christian hagiography, best known as the dragon-plagued city saved by Saint George in medieval narratives.
E2062463 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: city of Silene | Statement: [Medieval Lives of Saint George, setting, city of Silene]
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: city of Silene
Triple: [Medieval Lives of Saint George, setting, city of Silene]
Generated description
The city of Silene is a legendary locale in Christian hagiography, best known as the dragon-plagued city saved by Saint George in medieval narratives.

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_69f3498280c48190bcc3494017d14234 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f9bf21c48190b3013e83855aa91f completed May 3, 2026, 7:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36271c0fc88190a41a5709301c5829 completed June 20, 2026, 5:37 a.m.
NEDg Description generation batch_6a36366f5dc481908707e1be19c65643 completed June 20, 2026, 6:42 a.m.
NED2 Entity disambiguation (via description) batch_6a36371722348190a9043ec9d4619faf completed June 20, 2026, 6:45 a.m.
Created at: May 1, 2026, 1:42 a.m.