Triple

T14098868
Position Surface form Disambiguated ID Type / Status
Subject Rumuigbo E339325 entity
Predicate near P350 FINISHED
Object Rumueme E338073 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: Rumueme | Statement: [Rumuigbo, near, Rumueme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rumueme
Context triple: [Rumuigbo, near, Rumueme]
  • A. Rumueme chosen
    Rumueme is a prominent urban community in Rivers State, Nigeria, forming part of the greater Port Harcourt metropolitan area.
  • B. Rumuomasi
    Rumuomasi is a community in Port Harcourt, Rivers State, Nigeria, known as one of the city’s residential and commercial neighborhoods.
  • C. Rumbia
    Rumbia is a town in Indonesia’s Southeast Sulawesi province that serves as a local administrative and population center.
  • D. Rumuolumeni
    Rumuolumeni is a suburban community in Port Harcourt, Rivers State, Nigeria, known for hosting educational institutions and industrial facilities.
  • E. Ye’kuana
    The Ye’kuana are an Indigenous people of the Amazonian region of Venezuela and Brazil, known for their riverine village life, intricate basketry, and rich oral traditions.
  • 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_69d81c69b5c8819094aa1abf18302908 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5fba7c10819095b1299b7b4f0310 completed April 14, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd0adfc28819097a1bfd56739c286 completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:22 p.m.