Triple

T7051158
Position Surface form Disambiguated ID Type / Status
Subject Pasan language E163767 entity
Predicate hasAlternativeName P39 FINISHED
Object Toundano E645303 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: Toundano | Statement: [Pasan language, hasAlternativeName, Toundano]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Toundano
Context triple: [Pasan language, hasAlternativeName, Toundano]
  • A. Toundano chosen
    Toundano is an alternative name for the Tondano language, an Austronesian language spoken in North Sulawesi, Indonesia.
  • B. Kuanua
    Kuanua is an Austronesian language spoken primarily by the Tolai people of East New Britain in Papua New Guinea.
  • C. Tantamani
    Tantamani was a Kushite king of the 25th Dynasty of Egypt, known for his brief attempt to restore Nubian control over Egypt before being driven back by the Assyrians.
  • D. Vangunu
    Vangunu is an Oceanic language of the Meso-Melanesian group spoken on Vangunu Island in the Solomon Islands.
  • E. Nawuli
    Nawuli is an alternative name for the Nawuri language, a Guang language spoken primarily in parts of Ghana.
  • 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_69c6885f598c8190b6b6495c59d8d962 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e2500570819087200013d859cfe6 completed March 27, 2026, 8:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7b8c5a9fc81909a94e8e6c287b591 completed March 28, 2026, 11:17 a.m.
Created at: March 27, 2026, 2:37 p.m.