Triple

T4976678
Position Surface form Disambiguated ID Type / Status
Subject gon E111781 entity
Predicate hasPrimarySpeakers P18995 FINISHED
Object indigenous community 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: indigenous community | Statement: [gon, hasPrimarySpeakers, indigenous community]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPrimarySpeakers
Context triple: [gon, hasPrimarySpeakers, indigenous community]
  • A. hasMainSpeaker
    Indicates that one entity serves as the primary or principal speaker associated with another entity, such as an event, recording, or presentation.
  • B. hasSpeakersIn
    Indicates that an entity (such as an event, conference, or session) includes or is associated with speakers located in or belonging to a specified place or group.
  • C. hasSpeakerType
    Indicates that an entity functions in a particular role or category as a speaker (e.g., narrator, character, announcer) within a given context.
  • D. primarySpeakers chosen
    Indicates the entities that are the main or most significant speakers associated with another entity (such as an event, recording, or language).
  • E. hasNativeSpeakers
    Indicates that a language or dialect is spoken as a first language by one or more people or populations.
  • 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_69bd441adc208190b70a033a0741d01e completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd730a7590819088ab8d49c5c88c2f completed March 20, 2026, 4:17 p.m.
PD Predicate disambiguation batch_69bd7146e6e881908a55ab2756b631f6 completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:33 p.m.