Triple
T14098866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumuigbo |
E339325
|
entity |
| Predicate | hasRoadConnectionTo |
P11435
|
FINISHED |
| Object | Rumuokwuta |
E341200
|
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: Rumuokwuta | Statement: [Rumuigbo, hasRoadConnectionTo, Rumuokwuta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rumuokwuta Context triple: [Rumuigbo, hasRoadConnectionTo, Rumuokwuta]
-
A.
Rumuokwuta
chosen
Rumuokwuta is a prominent urban town in Rivers State, Nigeria, forming part of the greater Port Harcourt metropolitan area.
-
B.
Rumuokwurusi
Rumuokwurusi is a prominent urban town in Rivers State, Nigeria, known for its commercial activity and strategic location within the Port Harcourt metropolitan area.
-
C.
Rumuolumeni
Rumuolumeni is a suburban community in Port Harcourt, Rivers State, Nigeria, known for hosting educational institutions and industrial facilities.
-
D.
Rumuigbo
Rumuigbo is a prominent suburban town in Rivers State, Nigeria, situated within the greater Port Harcourt metropolitan area.
-
E.
Ojowo
Ojowo is a town within the Ijebu North area of Ogun State in southwestern Nigeria.
- 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_69fcdf02638881908eff75453b6a2aab |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 10:22 p.m.