Triple

T18265116
Position Surface form Disambiguated ID Type / Status
Subject Forro language E437462 entity
Predicate hasNeighborLanguage P16383 FINISHED
Object Angolar 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: Angolar language | Statement: [Forro language, hasNeighborLanguage, Angolar language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Angolar language
Context triple: [Forro language, hasNeighborLanguage, Angolar language]
  • A. Angolar language chosen
    Angolar is a Portuguese-based creole language spoken primarily by the Angolar community on São Tomé Island in São Tomé and Príncipe.
  • B. Awngi language
    The Awngi language is a Central Cushitic (Agaw) language spoken primarily in northwestern Ethiopia by the Awi people.
  • C. Annang language
    The Annang language is a Niger-Congo language spoken primarily by the Annang people of southern Nigeria, closely associated with the Ibibio-Efik linguistic cluster.
  • D. Anakalangu language
    The Anakalangu language is an Austronesian language spoken by communities on the island of Sumba in eastern Indonesia.
  • E. Angas languages
    Angas languages are a group of closely related Chadic languages spoken primarily in central Nigeria.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ff79851481909a4bbeb14fb00647 completed April 19, 2026, 4:14 p.m.
Created at: April 10, 2026, 10:34 a.m.