Triple

T5379740
Position Surface form Disambiguated ID Type / Status
Subject Tuscarora language E113051 entity
Predicate speakers P63645 FINISHED
Object very few fluent speakers 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: very few fluent speakers | Statement: [Tuscarora language, speakers, very few fluent speakers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: speakers
Context triple: [Tuscarora language, speakers, very few fluent speakers]
  • A. 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.
  • B. primarySpeakers
    Indicates the entities that are the main or most significant speakers associated with another entity (such as an event, recording, or language).
  • C. usedBySpeakers
    Indicates that something (such as a resource, tool, or method) is employed or utilized by speakers.
  • D. traditionalSpeakers
    Indicates that the subject speaks a language in its traditional or heritage form, typically as part of a longstanding cultural or community practice.
  • E. speakerType
    Indicates the role or category of a participant in a communicative act (e.g., narrator, quoted speaker, system voice) within a given context.
  • 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_69bd4436a1988190af18dcff7fd306b4 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd88801b188190b9ac35ed89167fa3 completed March 20, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69bd846172788190969f24bc7503c05e completed March 20, 2026, 5:31 p.m.
PDg Predicate description generation batch_69bd887f5b0081909456992d1a071928 completed March 20, 2026, 5:48 p.m.
Created at: March 20, 2026, 2:03 p.m.