Triple

T3187906
Position Surface form Disambiguated ID Type / Status
Subject Central African Republic E66746 entity
Predicate officialLanguage P236 FINISHED
Object Sango E274564 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: Sango | Statement: [Central African Republic, officialLanguage, Sango]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sango
Context triple: [Central African Republic, officialLanguage, Sango]
  • A. Sango chosen
    Sango is a Central African lingua franca and national language of the Central African Republic, originating as a Ngbandi-based trade language.
  • B. Tanno
    Tanno is a district or locality within the city of Kitami in Hokkaido, Japan.
  • C. Shingu
    Shingu is a coastal city in Japan known for its historic Kumano Hongu Taisha shrine and its role as a gateway to the sacred Kumano Kodo pilgrimage routes.
  • D. Nakanamanga
    Nakanamanga is an Oceanic Austronesian language spoken primarily on Efate Island and nearby areas in Vanuatu.
  • E. Sonamura
    Sonamura is a town in the Indian state of Tripura, known as an administrative and commercial center near the India–Bangladesh border.
  • 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_69ad8587c1bc8190a2595f2c22ee1001 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada6e279288190843837751e852c9e completed March 8, 2026, 4:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69b24b8c075881909152ddca48b7da60 completed March 12, 2026, 5:13 a.m.
Created at: March 8, 2026, 3:06 p.m.