Triple
T15107194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nhava Sheva (JNPT) |
E360817
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | JNPT |
E919087
|
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: JNPT | Statement: [Nhava Sheva (JNPT), alsoKnownAs, JNPT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JNPT Context triple: [Nhava Sheva (JNPT), alsoKnownAs, JNPT]
-
A.
JNPT
chosen
JNPT (Jawaharlal Nehru Port Trust) is India’s largest container port, located near Mumbai on the Arabian Sea coast in Maharashtra.
-
B.
NJP
NJP is the abbreviation commonly used for the New Japan Philharmonic, a prominent Japanese symphony orchestra based in Tokyo.
-
C.
JPTYO
JPTYO is the UN/LOCODE identifier for the Port of Tokyo, a major international seaport serving Japan’s capital city.
-
D.
JNPR
JNPR is the stock ticker symbol for Juniper Networks, a multinational company specializing in networking products and services such as routers, switches, and security solutions.
-
E.
JDNT
JDNT is a component or subdivision within Zaba, likely representing a specific unit, department, or feature of that larger entity.
- 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_69feb7e912ac8190bd0e0c9cdbbd0194 |
completed | May 9, 2026, 4:28 a.m. |
Created at: April 10, 2026, 3:05 a.m.