Triple
T16054718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mormugao |
E389447
|
entity |
| Predicate | hasHarbor |
P3007
|
FINISHED |
| Object | Mormugao Harbor |
E146003
|
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: Mormugao Harbor | Statement: [Mormugao, hasHarbor, Mormugao Harbor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mormugao Harbor Context triple: [Mormugao, hasHarbor, Mormugao Harbor]
-
A.
Mormugao Port
chosen
Mormugao Port is a major natural harbor and one of India’s leading iron ore exporting ports, located in the state of Goa on the Arabian Sea.
-
B.
Kamarajar Port
Kamarajar Port is a major deep-water seaport near Chennai on India’s east coast, serving as a key hub for cargo and industrial maritime trade.
-
C.
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.
-
D.
Mundra Port
Mundra Port is India’s largest commercial port and a major deep-draft, all-weather cargo hub located on the Arabian Sea coast in the state of Gujarat.
-
E.
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.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e183642420819088b03f613ee65851 |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff29836bc8190b35f528d3e8547be |
completed | May 10, 2026, 2:51 a.m. |
Created at: April 10, 2026, 4:56 a.m.