Triple

T33924358
Position Surface form Disambiguated ID Type / Status
Subject Pazyryk burial ground E869706 entity
Predicate hasPart P35 FINISHED
Object Pazyryk kurgan 5
Pazyryk kurgan 5 is one of the large Scythian-era burial mounds in the Altai Mountains, notable for its well-preserved archaeological finds and frozen tombs.
E869706 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: Pazyryk kurgan 5 | Statement: [Pazyryk burial ground, hasPart, Pazyryk kurgan 5]
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: Pazyryk kurgan 5
Triple: [Pazyryk burial ground, hasPart, Pazyryk kurgan 5]
Generated description
Pazyryk kurgan 5 is one of the large Scythian-era burial mounds in the Altai Mountains, notable for its well-preserved archaeological finds and frozen tombs.

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_69f349992c508190aa4afa24a086cc8c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f701f03ffc8190b39e191e44730d24 completed May 3, 2026, 8:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36ae362068819088c4a3e396bc510f completed June 20, 2026, 3:13 p.m.
NEDg Description generation batch_6a36af0ecea8819092b60c42572f3865 completed June 20, 2026, 3:17 p.m.
NED2 Entity disambiguation (via description) batch_6a36afaee2b88190b603b07a7700efa2 completed June 20, 2026, 3:20 p.m.
Created at: May 1, 2026, 1:49 a.m.