Triple

T5272229
Position Surface form Disambiguated ID Type / Status
Subject Slavey E119285 entity
Predicate hasExonymOrigin P4705 FINISHED
Object term given by neighboring peoples and Europeans 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: term given by neighboring peoples and Europeans | Statement: [Slavey, hasExonymOrigin, term given by neighboring peoples and Europeans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasExonymOrigin
Context triple: [Slavey, hasExonymOrigin, term given by neighboring peoples and Europeans]
  • A. hasExonym chosen
    Indicates that one entity is known by an alternative name or designation in another language or cultural context.
  • B. exonymStatus
    Indicates the status or classification of a name used in one language to refer to a place, people, or entity known by a different name in its own language.
  • C. hasEndonym
    Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
  • D. hasLanguageOfOrigin
    Indicates that one entity has its origin or source in the language specified by another entity.
  • E. hasEthnonymCountry
    Indicates that an ethnonym (a name for an ethnic group or people) is associated with or pertains to a specific country.
  • 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_69bd446c38e081908cdaf113bdf86790 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7d5a23908190a24e79d1b29d6fcf completed March 20, 2026, 5:01 p.m.
PD Predicate disambiguation batch_69bd77c71268819094f9f5203eed392d completed March 20, 2026, 4:37 p.m.
Created at: March 20, 2026, 1:51 p.m.