Triple
T3465648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundra Port |
E73129
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Mundra |
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 | Statement: [Mundra Port, locatedIn, Mundra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mundra Context triple: [Mundra Port, locatedIn, Mundra]
-
A.
Vengurla
Vengurla is a coastal town in Maharashtra, India, known for its scenic beaches, historic forts, and cashew plantations.
-
B.
Kanchrapara
Kanchrapara is a town in the North 24 Parganas district of West Bengal, India, known historically for its railway workshop and suburban connectivity to Kolkata.
-
C.
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.
-
D.
Nanakramguda
Nanakramguda is a prominent IT and financial district in Hyderabad, India, known for housing major technology parks, corporate offices, and the city’s financial services hub.
-
E.
Vikrampura
Vikrampura was an important historical city that served as a principal royal center of the medieval Indian Pala dynasty in eastern India.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb0f2d3881908a5fa871341564ed |
completed | March 8, 2026, 6:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3680412c0819086da51a05b24a676 |
completed | March 13, 2026, 1:27 a.m. |
Created at: March 8, 2026, 3:17 p.m.