Triple
T14491988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gujarat |
E359383
|
entity |
| Predicate | hasMajorPort |
P942
|
FINISHED |
| Object | Mundra Port |
E73129
|
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: Mundra Port | Statement: [Gujarat, hasMajorPort, Mundra Port]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mundra Port Context triple: [Gujarat, hasMajorPort, Mundra Port]
-
A.
Mundra Port
chosen
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.
-
B.
Paradip Port
Paradip Port is a major deep-water seaport on the east coast of India that serves as a key hub for maritime trade and cargo handling in the Bay of Bengal region.
-
C.
Kandla Port
Kandla Port is a major commercial seaport on the western coast of India, serving as one of the country’s key hubs for maritime trade and cargo handling.
-
D.
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.
-
E.
Pipavav Port
Pipavav Port is a major private deep-water port on India’s western coast, serving as an important hub for container, bulk, and liquid cargo trade.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930d820481908b9813014dd02540 |
completed | April 14, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feadfaddc88190bb1196ace0bfd4ff |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 1:20 a.m.