Triple

T27784658
Position Surface form Disambiguated ID Type / Status
Subject Temple 16 (Copán) E700926 entity
Predicate hasSubstructure P35 FINISHED
Object Yehnal temple
The Yehnal temple is an architectural substructure within the ancient Maya site of Copán, likely representing an earlier construction phase or ceremonial building beneath Temple 16.
E1788804 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: Yehnal temple | Statement: [Temple 16 (Copán), hasSubstructure, Yehnal temple]
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: Yehnal temple
Triple: [Temple 16 (Copán), hasSubstructure, Yehnal temple]
Generated description
The Yehnal temple is an architectural substructure within the ancient Maya site of Copán, likely representing an earlier construction phase or ceremonial building beneath Temple 16.

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_69ef6a50d8088190acbf3dfbb06d8091 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f637d14af48190853835015359ec9d completed May 2, 2026, 5:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12ecc61728819095cad91e0fa3ab4f completed May 24, 2026, 12:19 p.m.
NEDg Description generation batch_6a12ed68ab588190a2247672cc7818d8 completed May 24, 2026, 12:22 p.m.
NED2 Entity disambiguation (via description) batch_6a12ee56948881908c58657e262882a0 completed May 24, 2026, 12:25 p.m.
Created at: April 27, 2026, 5:24 p.m.