Triple
T10605967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INBOM |
E275876
|
entity |
| Predicate | designates |
P974
|
FINISHED |
| Object | Mumbai Port |
E67210
|
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: Mumbai Port | Statement: [INBOM, designates, Mumbai Port]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mumbai Port Context triple: [INBOM, designates, Mumbai Port]
-
A.
Indoji Port
Indoji Port is a harbor facility located on Iki Island in Japan, serving as one of the island’s key maritime access points.
-
B.
Porbandar Port
Porbandar Port is a coastal seaport on the Arabian Sea in Gujarat, India, serving as a regional hub for maritime trade and fishing.
-
C.
Bhavnagar Port
Bhavnagar Port is a maritime port in the city of Bhavnagar, Gujarat, India, serving as a regional hub for coastal trade and shipping.
-
D.
Mumbai Harbour
chosen
Mumbai Harbour is a natural deep-water harbor on the eastern shore of Mumbai, India, serving as a major maritime gateway and commercial port on the Arabian Sea.
-
E.
Karwar Port
Karwar Port is a coastal seaport in Karnataka, India, serving as a regional maritime hub for trade, fishing, and naval operations along the Arabian Sea.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4a5df88190b993196ca7849a88 |
completed | April 8, 2026, 11:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d95eb726bc8190a8db7357bd126016 |
completed | April 10, 2026, 8:33 p.m. |
Created at: April 8, 2026, 7:32 p.m.