Triple

T23256683
Position Surface form Disambiguated ID Type / Status
Subject Temne E581892 entity
Predicate neighboringEthnicGroup P11274 FINISHED
Object Loko 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: Loko | Statement: [Temne, neighboringEthnicGroup, Loko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Loko
Context triple: [Temne, neighboringEthnicGroup, Loko]
  • A. Loko chosen
    Loko is a Mande language spoken primarily in parts of Sierra Leone by the Loko ethnic group.
  • B. Loko
    Loko is the popular nickname of Lokomotiv Yaroslavl, a professional ice hockey team based in Yaroslavl, Russia.
  • C. Lokosi
    Lokosi is the popular nickname of Croatian football club NK Lokomotiva Zagreb, used by its supporters and in local football culture.
  • D. Goëlo
    Goëlo is a historic coastal region in northern Brittany, France, that served as a key territorial stronghold for various Breton noble houses.
  • E. Liboi
    Liboi is a small Kenyan border town in the arid northeast near Somalia, serving as a local trading and transit point.
  • 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_69e246079f58819085eaa9c260906880 completed April 17, 2026, 2:39 p.m.
NER Named-entity recognition batch_69f194c4905c819099ca21c6529413ac completed April 29, 2026, 5:19 a.m.
Created at: April 17, 2026, 4:11 p.m.