Triple

T7007193
Position Surface form Disambiguated ID Type / Status
Subject Simbo language E162485 entity
Predicate hasAlternativeName P39 FINISHED
Object Simbo E146930 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: Simbo | Statement: [Simbo language, hasAlternativeName, Simbo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Simbo
Context triple: [Simbo language, hasAlternativeName, Simbo]
  • A. Simbo chosen
    Simbo is an Oceanic language of the Meso-Melanesian subgroup spoken on Simbo Island in the Solomon Islands.
  • B. Nyaksimvol
    Nyaksimvol is a small rural locality in the Khanty-Mansi Autonomous Okrug of Russia, situated in the oil-rich region of Western Siberia.
  • C. Tiko
    Tiko is a coastal town and port in southwestern Cameroon known for its agricultural activities and role as a transport hub.
  • D. Shigmo
    Shigmo is a spring harvest and Holi-related folk festival celebrated with vibrant processions, traditional dances, and music in Goa and the Konkan region of India.
  • E. Shenwa
    Shenwa is a Zenati Berber language spoken by a small community in the Chenoua (Shenwa) region of northern Algeria.
  • 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_69c6885928148190ae31909fbb5e9849 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dc35cb848190a839919021efce81 completed March 27, 2026, 7:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69c76a43c3a081909b9150d36ba107f5 completed March 28, 2026, 5:42 a.m.
Created at: March 27, 2026, 2:33 p.m.