Triple

T11955009
Position Surface form Disambiguated ID Type / Status
Subject Ampato E284527 entity
Predicate hasNearbyArchaeologicalFinds P14422 FINISHED
Object Inca ceremonial sites 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: Inca ceremonial sites | Statement: [Ampato, hasNearbyArchaeologicalFinds, Inca ceremonial sites]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearbyArchaeologicalFinds
Context triple: [Ampato, hasNearbyArchaeologicalFinds, Inca ceremonial sites]
  • A. hasNearbyArchaeologicalSite chosen
    Indicates that an entity is located close to or in the vicinity of an archaeological site.
  • B. hasArchaeologicalExcavationsBy
    Indicates that archaeological excavations at a site or location are or were conducted by a specified person, group, or organization.
  • C. hasArchaeologicalFeature
    Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
  • D. hasArchaeologicalExcavationsSince
    Indicates that archaeological excavations have been conducted at an entity starting from a specified point in time and continuing since then.
  • E. hasArchaeologicalProject
    Indicates that an entity is associated with or involved in a specific archaeological project.
  • F. None of above.

Provenance (3 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_69d6ab2db38c8190b1f0ed6663ef8ada completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90366fda8819083168c93abad27d4 completed April 10, 2026, 2:04 p.m.
PD Predicate disambiguation batch_69d8bb3e48e08190b2fee43af4f57323 completed April 10, 2026, 8:56 a.m.
Created at: April 8, 2026, 9:45 p.m.