Triple

T29837636
Position Surface form Disambiguated ID Type / Status
Subject Cochin International Airport Limited E757696 entity
Predicate operatesTerminal P86510 FINISHED
Object Passenger terminals of Cochin International Airport LITERAL 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: Passenger terminals of Cochin International Airport | Statement: [Cochin International Airport Limited, operatesTerminal, Passenger terminals of Cochin International Airport]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatesTerminal
Context triple: [Cochin International Airport Limited, operatesTerminal, Passenger terminals of Cochin International Airport]
  • A. operatesTerminalsIn chosen
    Indicates that an entity manages or runs the operations of one or more terminals at a given location or facility.
  • B. terminal4Operator
    Indicates that an entity operates or manages the facilities, services, or activities associated with Terminal 4 of a larger transportation hub.
  • C. operateIn
    Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
  • D. terminal3Use
    Indicates that an entity makes use of or operates from terminal 3 (such as a specific terminal in a facility, station, or airport).
  • E. usedAsTerminalFor
    Indicates that one entity functions as the terminal endpoint or final connection point for another entity.
  • F. None of above.

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_69f224593f6c81908785a560fe659f58 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69ff32b88bf48190b45afd1b60cb511c completed May 9, 2026, 1:12 p.m.
PD Predicate disambiguation batch_69ff3031e18881908927b2ab452de863 completed May 9, 2026, 1:01 p.m.
Created at: April 29, 2026, 5:37 p.m.