Triple

T33329499
Position Surface form Disambiguated ID Type / Status
Subject Archbishop of St. Louis E853362 entity
Predicate precededBy P97 FINISHED
Object Bishop of St. Louis
The Bishop of St. Louis was the earlier Catholic episcopal office overseeing the Diocese of St. Louis before it was elevated to an archdiocese.
E853362 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: Bishop of St. Louis | Statement: [Archbishop of St. Louis, precededBy, Bishop of St. Louis]
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: Bishop of St. Louis
Triple: [Archbishop of St. Louis, precededBy, Bishop of St. Louis]
Generated description
The Bishop of St. Louis was the earlier Catholic episcopal office overseeing the Diocese of St. Louis before it was elevated to an archdiocese.

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_69f34969614c81909cd99661b0902533 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6df46df5081909a5eccdf6e8dbab6 completed May 3, 2026, 5:38 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3576dad3bc819095219b8d63f7138d completed June 19, 2026, 5:05 p.m.
NEDg Description generation batch_6a3578404d488190a72b580ac3af4eb1 completed June 19, 2026, 5:11 p.m.
NED2 Entity disambiguation (via description) batch_6a3578ce5b1c8190a2e0a5361a39dd80 completed June 19, 2026, 5:13 p.m.
Created at: May 1, 2026, 1:34 a.m.