Triple

T13937837
Position Surface form Disambiguated ID Type / Status
Subject Igede language E335164 entity
Predicate hasAlternativeName P39 FINISHED
Object Igede-Ito E363210 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: Igede-Ito | Statement: [Igede language, hasAlternativeName, Igede-Ito]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Igede-Ito
Context triple: [Igede language, hasAlternativeName, Igede-Ito]
  • A. Igede chosen
    Igede is an ethnic group in central Nigeria known for its distinct language, cultural festivals, and presence in and around Benue State.
  • B. Iwade
    Iwade is a village in Kent, England, situated near Sittingbourne in the Swale district.
  • C. Hieda
    Hieda is a Japanese surname notably associated with historical and literary figures in classical Japanese records and folklore.
  • D. Ichigaya
    Ichigaya is a central Tokyo district known for its major railway station, government and educational institutions, and proximity to the Imperial Palace area.
  • E. Ōtoku
    Ōtoku was a Japanese era name (nengō) of the late 11th century, used during the reign of Emperor Shirakawa.
  • 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2cf5cc8c8190bea74291702b2925 completed April 14, 2026, 12:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69fba1c81e988190a5fd8e2d83e065fe completed May 6, 2026, 8:17 p.m.
Created at: April 9, 2026, 10:17 p.m.