Triple

T21650710
Position Surface form Disambiguated ID Type / Status
Subject Marovo language E534328 entity
Predicate isRelatedTo P37 FINISHED
Object Ghanongga language 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: Ghanongga language | Statement: [Marovo language, isRelatedTo, Ghanongga language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ghanongga language
Context triple: [Marovo language, isRelatedTo, Ghanongga language]
  • A. Ghanongga language chosen
    The Ghanongga language is an Oceanic language spoken by indigenous communities on New Georgia Island in the Solomon Islands.
  • B. Gonja language
    The Gonja language is a Gur language spoken primarily by the Gonja people in northern Ghana.
  • C. Gahuku language
    Gahuku language is a Papuan language spoken by the Gahuku people in Papua New Guinea.
  • D. Ganguela language
    The Ganguela language is a Bantu language spoken by the Ganguela people of southwestern Africa, particularly in Angola.
  • E. Gathang language
    Gathang language is an Aboriginal Australian language traditionally spoken by the Worimi and neighboring peoples of the mid-north coast of New South Wales.
  • 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_69e0c466aec88190ba39c7543dbc8ba2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef5913cd9c81908a6ce9bc741416bf completed April 27, 2026, 12:39 p.m.
Created at: April 16, 2026, 6:35 p.m.