Triple
T15107112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipavav |
E360815
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Port of Pipavav |
E73499
|
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: Port of Pipavav | Statement: [Pipavav, hasPort, Port of Pipavav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Port of Pipavav Context triple: [Pipavav, hasPort, Port of Pipavav]
-
A.
Pipavav Port
chosen
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.
-
B.
Hazira Port
Hazira Port is a deep-water port on the Arabian Sea near Surat in Gujarat, India, serving as a key hub for container, bulk, and liquid cargo handling.
-
C.
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.
-
D.
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.
-
E.
Navlakhi Port
Navlakhi Port is a minor commercial seaport in Gujarat, India, serving as a regional hub for handling bulk cargo along the Gulf of Kutch.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058af8988190977d998f85893836 |
completed | April 15, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef88bc8088190a357657c461f761d |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:05 a.m.