Triple

T34652940
Position Surface form Disambiguated ID Type / Status
Subject Monte Santo E889887 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object Igreja do Monte Santo
Igreja do Monte Santo is a Catholic church that serves as a key place of worship and local religious landmark in the town of Monte Santo, Brazil.
E2105395 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: Igreja do Monte Santo | Statement: [Monte Santo, hasReligiousBuilding, Igreja do Monte Santo]
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: Igreja do Monte Santo
Triple: [Monte Santo, hasReligiousBuilding, Igreja do Monte Santo]
Generated description
Igreja do Monte Santo is a Catholic church that serves as a key place of worship and local religious landmark in the town of Monte Santo, Brazil.

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_69f349d825c88190bfc6170ac9281260 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f722c4fd388190a269f97bb31e6656 completed May 3, 2026, 10:26 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3748f9896481908fbc8f56c38946f9 completed June 21, 2026, 2:14 a.m.
NEDg Description generation batch_6a37497c1b848190aade6d8736ae7330 completed June 21, 2026, 2:16 a.m.
NED2 Entity disambiguation (via description) batch_6a374a3215c881908150136512f90f71 completed June 21, 2026, 2:19 a.m.
Created at: May 1, 2026, 2:04 a.m.