Triple

T23429228
Position Surface form Disambiguated ID Type / Status
Subject Puluwatese people E563277 entity
Predicate ethnologueCodeForLanguage P36930 FINISHED
Object puw 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: puw | Statement: [Puluwatese people, ethnologueCodeForLanguage, puw]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ethnologueCodeForLanguage
Context triple: [Puluwatese people, ethnologueCodeForLanguage, puw]
  • A. ISO639-3CodeOfLanguage chosen
    Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other entity.
  • B. sharesISO639-3CodeWith
    Indicates that two language entities share the same ISO 639-3 code, meaning they are treated as the same language in that coding system.
  • C. ISO639CollectiveCode
    Indicates that the relationship assigns or associates an ISO 639 collective language code (a code representing a group of related languages) to the relevant language entity or set of languages.
  • D. languageCodeISO639-2
    Indicates that an entity is associated with a language identified by its ISO 639-2 three-letter code.
  • E. ethnologueScope
    Indicates the classification scope or coverage category assigned to a language or variety within the Ethnologue system.
  • 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_69e24553980c8190bb66a2ae0bdab125 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1a54ba29881909945690496f28d65 completed April 29, 2026, 6:29 a.m.
PD Predicate disambiguation batch_69f061f92da081908e7f1d0cd1e9b01c completed April 28, 2026, 7:30 a.m.
Created at: April 17, 2026, 5:48 p.m.