Triple

T4074763
Position Surface form Disambiguated ID Type / Status
Subject Lima Airport Partners E86735 entity
Predicate airportCategoryManaged P424 FINISHED
Object primary international gateway 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: primary international gateway airport | Statement: [Lima Airport Partners, airportCategoryManaged, primary international gateway airport]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: airportCategoryManaged
Context triple: [Lima Airport Partners, airportCategoryManaged, primary international gateway airport]
  • A. airportRole
    Indicates that an entity serves a specific functional role or capacity within the context of an airport.
  • B. airportUse
    Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
  • C. hasAirportClassification chosen
    Indicates that an airport is assigned a specific classification or category based on defined criteria.
  • D. isCivilAirport
    Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
  • E. isPublicAirport
    Indicates that an airport is open for use by the general public rather than restricted to private or military operations.
  • 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_69aed93ebe448190a1f1686e28740ac9 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefc25e2e08190b3c048e1b8f85bbf completed March 9, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69aef9061d2481908307cafc9e9b32c0 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:39 p.m.