Triple

T6906934
Position Surface form Disambiguated ID Type / Status
Subject Oaxaca Valley E159835 entity
Predicate contains P35 FINISHED
Object Yagul E159837 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: Yagul | Statement: [Oaxaca Valley, contains, Yagul]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yagul
Context triple: [Oaxaca Valley, contains, Yagul]
  • A. Yagul chosen
    Yagul is an important pre-Columbian archaeological site in Oaxaca, Mexico, known for its well-preserved Zapotec ruins and hilltop fortress.
  • B. Yagüe
    Yagüe is a Spanish surname most notably associated with Juan Yagüe, a prominent general during the Spanish Civil War.
  • C. Puyuma
    Puyuma are an indigenous Austronesian ethnic group of southeastern Taiwan known for their distinct language, matrilineal social structure, and rich ceremonial traditions.
  • D. Gundunguri
    Gundunguri is an alternative name for the Gundungurra, an Aboriginal Australian people traditionally associated with the Southern Highlands and Blue Mountains region of New South Wales.
  • E. Pira-Yine
    Pira-Yine is an indigenous language of the Arawakan family spoken by the Yine people in the Amazonian region of Peru.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c68839ccb88190b4aa5cc1aca3448f completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6d98c3ab08190a1830c45578056ac completed March 27, 2026, 7:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69c74901aee08190a5e132200fd58c05 completed March 28, 2026, 3:20 a.m.
Created at: March 27, 2026, 2:25 p.m.