Triple

T26465104
Position Surface form Disambiguated ID Type / Status
Subject Culle E665739 entity
Predicate linguisticLandscape P17400 FINISHED
Object pre-Hispanic northern Peruvian Andes 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: pre-Hispanic northern Peruvian Andes | Statement: [Culle, linguisticLandscape, pre-Hispanic northern Peruvian Andes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: linguisticLandscape
Context triple: [Culle, linguisticLandscape, pre-Hispanic northern Peruvian Andes]
  • A. languageDiversity
    Indicates the degree to which multiple distinct languages are present and used within a given context or population.
  • B. linguisticStatusOfArea
    Indicates the linguistic status or condition that characterizes a particular geographic area.
  • C. languageVitality
    Indicates the degree to which a language is actively used, maintained, and transmitted within a community, reflecting its risk of endangerment or extinction.
  • D. linguisticArea chosen
    Indicates a regional context in which languages share features due to geographic proximity and contact rather than common genetic origin.
  • E. linguisticField
    Indicates that something pertains to or is associated with a particular area or subdiscipline within linguistics.
  • 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_69ee883e812c8190a9b5a9cdb87fee5e completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f61a17a7788190946f7e32d63cd43f completed May 2, 2026, 3:36 p.m.
PD Predicate disambiguation batch_69f611ab768c8190b1849c15a3e59dda completed May 2, 2026, 3 p.m.
Created at: April 27, 2026, 12:15 a.m.