Triple

T11166969
Position Surface form Disambiguated ID Type / Status
Subject Ipunu E264183 entity
Predicate usesLanguageCode P5196 FINISHED
Object puu 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: puu | Statement: [Ipunu, usesLanguageCode, puu]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesLanguageCode
Context triple: [Ipunu, usesLanguageCode, puu]
  • A. isLanguageOf
    Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
  • B. eligibleLanguage
    Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
  • C. languageCodeISO639-1 chosen
    Indicates that the subject entity is associated with the specified two-letter ISO 639-1 language code.
  • D. usesLanguageFamily
    Indicates that an entity communicates or operates using a language that belongs to a specified language family.
  • E. languageUse
    Indicates the language or languages an entity uses for communication, expression, or interaction.
  • 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_69d6aa9dafac8190bd90d2c74f661aa7 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e88843cc81909e503f0921c6d297 completed April 9, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69d75cec26fc8190a5497d186306f935 completed April 9, 2026, 8:01 a.m.
Created at: April 8, 2026, 9:29 p.m.