Triple

T38304460
Position Surface form Disambiguated ID Type / Status
Subject Parish Church of St. Stanislaus (Fara Church) E1032309 entity
Predicate alsoKnownAs P39 FINISHED
Object Fara Church
Fara Church is a historic Roman Catholic parish church dedicated to St. Stanislaus, notable for its religious significance and architectural heritage.
E2265004 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: Fara Church | Statement: [Parish Church of St. Stanislaus (Fara Church), alsoKnownAs, Fara 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: Fara Church
Triple: [Parish Church of St. Stanislaus (Fara Church), alsoKnownAs, Fara Church]
Generated description
Fara Church is a historic Roman Catholic parish church dedicated to St. Stanislaus, notable for its religious significance and architectural heritage.

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_69f76e0f2084819091299d021625c3fe completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fcc61ccb908190a14ccb7428014bbc completed May 7, 2026, 5:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a419e0cfa808190be81469914f4f6f9 completed June 28, 2026, 10:19 p.m.
NEDg Description generation batch_6a41a17a14b88190953e2d68137a28e5 completed June 28, 2026, 10:34 p.m.
NED2 Entity disambiguation (via description) batch_6a41a1e708048190a2d2943db529f3d8 completed June 28, 2026, 10:36 p.m.
Created at: May 3, 2026, 4:30 p.m.