Triple

T14050406
Position Surface form Disambiguated ID Type / Status
Subject Rumuola E338072 entity
Predicate locatedNear P294 FINISHED
Object Rumuodara E338074 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: Rumuodara | Statement: [Rumuola, locatedNear, Rumuodara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rumuodara
Context triple: [Rumuola, locatedNear, Rumuodara]
  • A. Rumuodara chosen
    Rumuodara is a prominent urban community in Rivers State, Nigeria, forming part of the greater Port Harcourt metropolitan area.
  • B. Rumuokparali
    Rumuokparali is a town in Obio-Akpor Local Government Area of Rivers State, Nigeria, known as one of the area’s significant urban settlements.
  • C. Rumuomasi
    Rumuomasi is a community in Port Harcourt, Rivers State, Nigeria, known as one of the city’s residential and commercial neighborhoods.
  • D. Romm
    Romm is a surname most notably associated with Soviet film director and screenwriter Mikhail Romm.
  • E. Rumuosi
    Rumuosi is a prominent town in Rivers State, Nigeria, situated within the Obio-Akpor Local Government Area and forming part of the greater Port Harcourt metropolitan region.
  • 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_69d81c664e48819088cbd8f433aeffe5 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de3c8a518081908ad030ba48b7b946 completed April 14, 2026, 1:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd099b7788190a7c309dba450e58f completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:20 p.m.