Triple

T7770087
Position Surface form Disambiguated ID Type / Status
Subject Southeastern India E179045 entity
Predicate hasPort P35 FINISHED
Object Kamarajar Port E69231 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: Kamarajar Port | Statement: [Southeastern India, hasPort, Kamarajar Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kamarajar Port
Context triple: [Southeastern India, hasPort, Kamarajar Port]
  • A. Kamarajar Port chosen
    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.
  • B. 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.
  • C. 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.
  • D. Pipavav Port
    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.
  • E. 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.
  • 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_69c69f30602c819082ab52cd4af5c592 completed March 27, 2026, 3:16 p.m.
NER Named-entity recognition batch_69c70438ca2481909114b0c434717109 completed March 27, 2026, 10:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8deb127048190a89c08b7778df8a4 completed March 29, 2026, 8:11 a.m.
Created at: March 27, 2026, 4:11 p.m.