Triple

T32505198
Position Surface form Disambiguated ID Type / Status
Subject John Foley (Jesuit) E830772 entity
Predicate notableWork P4 FINISHED
Object One Bread, One Body
One Bread, One Body is a widely sung contemporary Catholic hymn, especially associated with the post–Vatican II liturgical renewal and Eucharistic worship.
E2009977 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: One Bread, One Body | Statement: [John Foley (Jesuit), notableWork, One Bread, One Body]
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: One Bread, One Body
Triple: [John Foley (Jesuit), notableWork, One Bread, One Body]
Generated description
One Bread, One Body is a widely sung contemporary Catholic hymn, especially associated with the post–Vatican II liturgical renewal and Eucharistic worship.

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_69f349219cb8819087e120f509629c1b completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c449f89c8190b15e5a3087d7d5cb completed May 3, 2026, 3:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34705c1ed88190b4dc262c40face30 completed June 18, 2026, 10:25 p.m.
NEDg Description generation batch_6a34711d59148190bef0f5cc0177a0ca completed June 18, 2026, 10:28 p.m.
NED2 Entity disambiguation (via description) batch_6a3471ee70d881909bd9668f4d0eb45b completed June 18, 2026, 10:32 p.m.
Created at: May 1, 2026, 1 a.m.