Triple

T1104300
Position Surface form Disambiguated ID Type / Status
Subject Altai Mountains E25451 entity
Predicate hasArchaeologicalSiteType P23168 FINISHED
Object Scythian burial mounds LITERAL 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: Scythian burial mounds | Statement: [Altai Mountains, hasArchaeologicalSiteType, Scythian burial mounds]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalSiteType
Context triple: [Altai Mountains, hasArchaeologicalSiteType, Scythian burial mounds]
  • A. hasArchaeologicalValue
    Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
  • B. hasNearbyArchaeologicalSite
    Indicates that an entity is located close to or in the vicinity of an archaeological site.
  • C. notableArchaeologicalSite
    Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
  • D. cultSite
    Indicates a location that is or was used for religious or ritual worship activities.
  • E. hasHistoricSite
    Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
  • F. None of above. chosen

Provenance (4 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_69a49428d4448190b3b36991ceae87ce completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b9e1047481909af1cf8df2a01fff completed March 1, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69a4b7472c848190b0643872f67084a2 completed March 1, 2026, 10:01 p.m.
PDg Predicate description generation batch_69a4b7da38888190a118ef20ce4ae9aa completed March 1, 2026, 10:04 p.m.
Created at: March 1, 2026, 7:43 p.m.