Triple

T25102513
Position Surface form Disambiguated ID Type / Status
Subject South Papua Province E628767 entity
Predicate hasEthnicLanguageFamily P28863 FINISHED
Object Austronesian languages NE NERFINISHED

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: Austronesian languages | Statement: [South Papua Province, hasEthnicLanguageFamily, Austronesian languages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEthnicLanguageFamily
Context triple: [South Papua Province, hasEthnicLanguageFamily, Austronesian languages]
  • A. hasIndigenousLanguageFamily chosen
    Indicates that an entity’s indigenous language belongs to, or is classified under, a particular language family.
  • B. usesLanguageFamily
    Indicates that an entity communicates or operates using a language that belongs to a specified language family.
  • C. hasEthnolinguisticPresence
    Indicates that a particular ethnolinguistic group is present or represented within a specified place, context, or population.
  • D. inLanguageFamily
    Indicates that two languages belong to the same linguistic family or classification.
  • E. isInLanguageFamily
    Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
  • 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_69e2ff3071548190b62d1ac237397197 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f497bc12b881908fe3386c66252bf6 completed May 1, 2026, 12:08 p.m.
PD Predicate disambiguation batch_69f49366e8d08190adb4b71fe3a14683 completed May 1, 2026, 11:49 a.m.
Created at: April 18, 2026, 6:26 a.m.