Triple
T11858353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Ijaw |
E282096
|
entity |
| Predicate | headquarters |
P62
|
FINISHED |
| Object | Oporoma |
E951716
|
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: Oporoma | Statement: [Southern Ijaw, headquarters, Oporoma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oporoma Context triple: [Southern Ijaw, headquarters, Oporoma]
-
A.
Oporoma
chosen
Oporoma is a town in Bayelsa State, Nigeria, serving as an administrative and political center for the surrounding Southern Ijaw area.
-
B.
Arpora
Arpora is a village in the Indian state of Goa, known for its popular Saturday Night Market and proximity to major beach destinations like Baga and Calangute.
-
C.
Ogori
Ogori is a small Japanese city located in Fukuoka Prefecture on the island of Kyushu.
-
D.
Oribos
Oribos is the central hub city and afterlife crossroads in World of Warcraft: Shadowlands, where players gather, trade, and access the expansion’s various realms.
-
E.
Aptoryama
Aptoryama is a specific Vedic soma sacrifice ritual recognized as a variant form of the Somayajna.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a699089c8190b7a298baf13dcded |
completed | April 10, 2026, 7:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f417a954e881909fdd9626d41229e2 |
completed | May 1, 2026, 3:02 a.m. |
Created at: April 8, 2026, 9:43 p.m.