Triple

T30769254
Position Surface form Disambiguated ID Type / Status
Subject Semelai E783464 entity
Predicate hasSpeakerCommunityStatus P191586 FINISHED
Object indigenous people of Malaysia 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 people of Malaysia | Statement: [Semelai, hasSpeakerCommunityStatus, indigenous people of Malaysia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSpeakerCommunityStatus
Context triple: [Semelai, hasSpeakerCommunityStatus, indigenous people of Malaysia]
  • A. hasSpeakerStatus
    Indicates that an entity holds a particular role, rank, or status in the context of speaking or serving as a speaker.
  • B. hasSpeakerIn
    Indicates that an event, work, or communication features a particular entity serving as its speaker.
  • 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. hasSpeakersAmong
    Indicates that a group, event, or entity includes one or more speakers drawn from a specified set or category.
  • E. 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.
  • F. None of above. chosen

Provenance (4 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_69f224b1519081908b9db003fd2073e0 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fce28d6c3081908bf76f5db63ecf68 completed May 7, 2026, 7:05 p.m.
PD Predicate disambiguation batch_69fce12d2f08819082134b5eb3db6a24 completed May 7, 2026, 6:59 p.m.
PDg Predicate description generation batch_69fce28a74508190aab36551094e8226 completed May 7, 2026, 7:05 p.m.
Created at: April 29, 2026, 8:40 p.m.