Triple

T19495549
Position Surface form Disambiguated ID Type / Status
Subject Nendö language E487759 entity
Predicate alternateName P39 FINISHED
Object Nendö 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: Nendö | Statement: [Nendö language, alternateName, Nendö]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nendö
Context triple: [Nendö language, alternateName, Nendö]
  • A. Nendö chosen
    Nendö is the largest island in the Santa Cruz Islands of the Solomon Islands, known for its remote location and traditional Melanesian culture.
  • B. Dondo
    Dondo is an Austronesian language spoken in Central Sulawesi, Indonesia, belonging to the Tomini–Tolitoli subgroup.
  • C. Dondo
    Dondo is a town and district in central Mozambique known as an important railway and industrial hub near the port city of Beira in Sofala Province.
  • D. Nisswa
    Nisswa is a small resort city in central Minnesota known for its lakes, tourism, and outdoor recreation.
  • E. Nednai
    Nednai is an alternate name for the Nednhi Apache, a subgroup of the Chiricahua Apache people historically living in northern Mexico and the U.S. Southwest.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d9d1c88190b01cd78b8be49384 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63490c16481908423e304d82722d7 completed April 20, 2026, 2:13 p.m.
Created at: April 10, 2026, 1:40 p.m.