Triple
T12963167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onne Port |
E321196
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Onne |
E382246
|
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: Onne | Statement: [Onne Port, locatedIn, Onne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Onne Context triple: [Onne Port, locatedIn, Onne]
-
A.
Onne
chosen
Onne is a port town in Rivers State, Nigeria, known for its major oil and gas logistics base and deepwater port facilities.
-
B.
Onn
Onn is a Malaysian family name most prominently associated with political figures such as former Prime Minister Hussein Onn.
-
C.
Unna
Unna is a town in the German state of North Rhine-Westphalia, known historically as a regional trading center near Dortmund.
-
D.
Odda
Odda is a town in western Norway known for its dramatic fjord landscape, industrial heritage, and proximity to popular hiking destinations like Trolltunga.
-
E.
Onan
Onan is a biblical figure from the Book of Genesis, known as the second son of Judah whose refusal to fulfill his levirate duty led to his death by divine judgment.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e2f5e448190b56e74602c43358d |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8e227948190a2d08db97b4e41aa |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 8:24 p.m.