Triple

T2674442
Position Surface form Disambiguated ID Type / Status
Subject Kakinada E56424 entity
Predicate hasPort P35 FINISHED
Object Kakinada Port E180969 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: Kakinada Port | Statement: [Kakinada, hasPort, Kakinada Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kakinada Port
Context triple: [Kakinada, hasPort, Kakinada Port]
  • A. Kakinada Port chosen
    Kakinada Port is a significant commercial seaport on the eastern coast of India, serving as a key maritime gateway for trade in Andhra Pradesh and the Bay of Bengal region.
  • B. Visakhapatnam Port
    Visakhapatnam Port is one of India’s largest and busiest seaports on the eastern coast, serving as a major hub for maritime trade and industry.
  • C. Krishnapatnam Port
    Krishnapatnam Port is a major deep-water seaport on India’s eastern coast, serving as a key hub for cargo and maritime trade in the state of Andhra Pradesh.
  • D. Kamarajar Port
    Kamarajar Port is a major deep-water seaport near Chennai on India’s east coast, serving as a key hub for cargo and industrial maritime trade.
  • E. 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.
  • 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_69ab4a4b13fc81909dfdb3f23da46832 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd9b228cc819097f045b4a51d8e7c completed March 7, 2026, 7:54 a.m.
NED1 Entity disambiguation (via context triple) batch_69afa06170108190a6f4be82fa4ecd2a completed March 10, 2026, 4:38 a.m.
Created at: March 6, 2026, 9:54 p.m.