Triple

T6690609
Position Surface form Disambiguated ID Type / Status
Subject Nalik E152615 entity
Predicate hasAlternativeName P39 FINISHED
Object Nalik language E155831 NE 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: Nalik language | Statement: [Nalik, hasAlternativeName, Nalik language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nalik language
Context triple: [Nalik, hasAlternativeName, Nalik language]
  • A. Nalik language chosen
    The Nalik language is an Austronesian language spoken primarily on New Ireland in Papua New Guinea by the Nalik people.
  • B. Nomlaki language
    The Nomlaki language is an endangered Native American language traditionally spoken by the Nomlaki people of northern California.
  • C. Lakalai language
    The Lakalai language is an Austronesian language spoken by the Lakalai people of New Britain in Papua New Guinea.
  • D. Nitinaht language
    The Nitinaht language is a Southern Wakashan Indigenous language spoken by the Ditidaht (Nitinaht) people of Vancouver Island in British Columbia, Canada.
  • E. Balantak language
    The Balantak language is an Austronesian language spoken by the Balantak people of eastern Central Sulawesi, Indonesia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c6880687b08190805278b504d1c92c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6b15276208190b4c0e90ca337d2b4 completed March 27, 2026, 4:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6f7b519148190a810d0eee7cda734 completed March 27, 2026, 9:33 p.m.
Created at: March 27, 2026, 2:04 p.m.