Triple

T14717902
Position Surface form Disambiguated ID Type / Status
Subject Edo language E345731 entity
Predicate alternativeName P39 FINISHED
Object Bini language E286632 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: Bini language | Statement: [Edo language, alternativeName, Bini language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bini language
Context triple: [Edo language, alternativeName, Bini language]
  • A. Bini language chosen
    Bini language is an Edoid language of southern Nigeria, primarily spoken by the Edo (Bini) people around Benin City.
  • B. Bipi language
    The Bipi language is an Oceanic Austronesian language spoken by the Bipi people of the Admiralty Islands in Papua New Guinea.
  • C. Bintauna language
    The Bintauna language is an Austronesian language spoken by the Bintauna people in North Sulawesi, Indonesia.
  • D. Bina language
    Bina language is an extinct Austronesian language once spoken in Papua New Guinea, belonging to the Papuan Tip subgroup.
  • E. Tindi language
    The Tindi language is a Northeast Caucasian language spoken by the Tindi people in Dagestan, Russia, known for its complex grammar and limited number of speakers.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb98688f48190b2b19ce7aa06a6db completed April 14, 2026, 10:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb8624bc8190b20441c2f5c4a2fa completed May 8, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:29 a.m.