Triple

T12653840
Position Surface form Disambiguated ID Type / Status
Subject Toma E302230 entity
Predicate hasAlternativeName P39 FINISHED
Object Loghoma E996629 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: Loghoma | Statement: [Toma, hasAlternativeName, Loghoma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Loghoma
Context triple: [Toma, hasAlternativeName, Loghoma]
  • A. Loghoma chosen
    Loghoma is an alternative name for the Loma people, an ethnic group primarily found in Liberia and neighboring West African regions.
  • B. Rozogi
    Rozogi is a village in northern Poland that serves as a local administrative and service center within the Warmian-Masurian Voivodeship.
  • C. Sarma
    Sarma is a traditional dish of vine or cabbage leaves wrapped around a savory filling, commonly enjoyed throughout Turkish and other Balkan and Middle Eastern cuisines.
  • D. Meehni
    Meehni is one of the three iconic sandstone rock pillars known as the Three Sisters in the Blue Mountains of New South Wales, Australia.
  • E. Kanchipuri
    Kanchipuri is another name for Kanchipuram, an ancient South Indian city renowned for its historic temples and silk saree weaving tradition.
  • 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_69d7bded71a88190bb76e2413af9ea66 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96160730c81909e1aa3efb51bf159 completed April 10, 2026, 8:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6719c18508190a9c28b2526e6b336 completed May 2, 2026, 9:50 p.m.
Created at: April 9, 2026, 5:18 p.m.