Triple
T2677455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warri |
E56493
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Warri Port |
E56493
|
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: Warri Port | Statement: [Warri, hasPort, Warri Port]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Warri Port Context triple: [Warri, hasPort, Warri Port]
-
A.
Warri
chosen
Warri is a prominent oil-producing and commercial city in southern Nigeria that serves as a key economic hub of the Niger Delta region.
-
B.
Yenagoa
Yenagoa is the capital city of Bayelsa State in southern Nigeria, located in the oil-rich Niger Delta region.
-
C.
Port Harcourt
Port Harcourt is a major oil and industrial city in southern Nigeria and the capital of Rivers State.
-
D.
Bata Port
Bata Port is a major seaport in Bata, Equatorial Guinea, serving as an important hub for the country’s maritime trade and transportation.
-
E.
Port of Broome
The Port of Broome is a key deep-water maritime gateway in Western Australia’s Kimberley region, serving regional trade, offshore industry, and cruise tourism.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9b697fc8190a5ec8b75ee2ad238 |
completed | March 7, 2026, 7:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afa065a6f48190973a3b6c52aa23bf |
completed | March 10, 2026, 4:39 a.m. |
Created at: March 6, 2026, 9:54 p.m.