Triple

T14051877
Position Surface form Disambiguated ID Type / Status
Subject Mumbai Island E338110 entity
Predicate contains P35 FINISHED
Object Mumbai Port area E67210 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: Mumbai Port area | Statement: [Mumbai Island, contains, Mumbai Port area]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mumbai Port area
Context triple: [Mumbai Island, contains, Mumbai Port area]
  • A. Mumbai Harbour chosen
    Mumbai Harbour is a natural deep-water harbor on the eastern shore of Mumbai, India, serving as a major maritime gateway and commercial port on the Arabian Sea.
  • B. Mumbai waterfront
    The Mumbai waterfront is a prominent coastal stretch of the city featuring historic landmarks, promenades, and harbors along the Arabian Sea.
  • C. Vasai-Virar
    Vasai-Virar is a rapidly growing suburban city and municipal corporation in the northern part of the Mumbai metropolitan area in Maharashtra, India.
  • D. Kurla
    Kurla is a densely populated suburban neighborhood in Mumbai, India, known as a major residential, commercial, and transport hub of the city.
  • E. 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.
  • 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_69d81c664e48819088cbd8f433aeffe5 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de3c8bc54c8190a12f0fc056568538 completed April 14, 2026, 1:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd324133f8819088c0d80a4e8fb5be completed May 8, 2026, 12:45 a.m.
Created at: April 9, 2026, 10:20 p.m.