Triple

T26214005
Position Surface form Disambiguated ID Type / Status
Subject Zamora, Spain E655569 entity
Predicate hasLandmark P105 FINISHED
Object Church of San Torcuato
The Church of San Torcuato is a historic Roman Catholic church in Zamora, Spain, noted for its traditional architecture and religious significance in the region.
E1735999 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: Church of San Torcuato | Statement: [Zamora, Spain, hasLandmark, Church of San Torcuato]
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: Church of San Torcuato
Triple: [Zamora, Spain, hasLandmark, Church of San Torcuato]
Generated description
The Church of San Torcuato is a historic Roman Catholic church in Zamora, Spain, noted for its traditional architecture and religious significance in the region.

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_69ee5b49adb4819086545280d4ef6337 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f60d19d4648190bbee8ebc67164e60 completed May 2, 2026, 2:41 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11ebf74d1c81909014af12f8b2b976 completed May 23, 2026, 6:03 p.m.
NEDg Description generation batch_6a11ed7032308190bd06ce7f4ee31a7f completed May 23, 2026, 6:09 p.m.
NED2 Entity disambiguation (via description) batch_6a11f129a14c8190873d62432560e0c4 completed May 23, 2026, 6:25 p.m.
Created at: April 26, 2026, 8:53 p.m.