Triple

T2814768
Position Surface form Disambiguated ID Type / Status
Subject Muisca E54255 entity
Predicate modernLocationOfHunza P32046 FINISHED
Object Tunja region 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: Tunja region | Statement: [Muisca, modernLocationOfHunza, Tunja region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: modernLocationOfHunza
Context triple: [Muisca, modernLocationOfHunza, Tunja region]
  • A. distanceFrom Peshawar
    Indicates the spatial distance between a given location or entity and the city of Peshawar.
  • B. locatedInMountainRainShadowOf
    Indicates that one location lies in the rain shadow of a mountain or mountain range, receiving reduced precipitation because the mountains block prevailing moisture-bearing winds.
  • C. ianaLocation
    Indicates that an entity is associated with a specific geographic or network location identified using an IANA-defined naming or coding scheme.
  • D. locatedInModernAdministrativeRegion chosen
    Indicates that an entity is geographically situated within the boundaries of a current, officially recognized administrative region.
  • E. cultLocation
    Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
  • 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_69ab49de0af08190b3da69683be1e728 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde4d29488190a32461906dd9ea7e completed March 7, 2026, 8:14 a.m.
PD Predicate disambiguation batch_69abdd0740208190911dc9c9546a79ae completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:59 p.m.