Triple

T25423527
Position Surface form Disambiguated ID Type / Status
Subject Wanniassa E637049 entity
Predicate hasReligiousFacility P1191 FINISHED
Object St Anthony’s Catholic Church
St Anthony’s Catholic Church is a Roman Catholic parish church serving the local community in the Canberra suburb of Wanniassa, Australia.
E1694168 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: St Anthony’s Catholic Church | Statement: [Wanniassa, hasReligiousFacility, St Anthony’s Catholic Church]
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: St Anthony’s Catholic Church
Triple: [Wanniassa, hasReligiousFacility, St Anthony’s Catholic Church]
Generated description
St Anthony’s Catholic Church is a Roman Catholic parish church serving the local community in the Canberra suburb of Wanniassa, Australia.

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_69e75db58a1c8190891b9ff7c2f8414e completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f6be79b0819093a406e1f9b1348c completed May 2, 2026, 1:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10cbd18b2481909a8c5517dfdbfd73 completed May 22, 2026, 9:34 p.m.
NEDg Description generation batch_6a10ccbbd8748190af5429ed417fd61f completed May 22, 2026, 9:38 p.m.
NED2 Entity disambiguation (via description) batch_6a10cdbc645881909f0c2da445ee41f6 completed May 22, 2026, 9:42 p.m.
Created at: April 21, 2026, 1:57 p.m.