Triple

T25430878
Position Surface form Disambiguated ID Type / Status
Subject FUN E637248 entity
Predicate airportSupportsCargo P86085 FINISHED
Object yes 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: yes | Statement: [FUN, airportSupportsCargo, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: airportSupportsCargo
Context triple: [FUN, airportSupportsCargo, yes]
  • A. isCargoAirportCode
    Indicates that an airport code specifically designates an airport primarily used for cargo operations.
  • B. hasAirportAccessTo
    Indicates that one location or entity has direct access to another via an airport connection or service.
  • C. airportUse
    Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
  • D. airportTypePresent chosen
    Indicates that a specific type or category of airport is present or exists in relation to the referenced entity.
  • E. airportServesAs
    Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
  • 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_69e75db58a1c8190891b9ff7c2f8414e completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f6562fd3488190be1acd8c526a28d2 completed May 2, 2026, 7:53 p.m.
PD Predicate disambiguation batch_69f651a731508190bb0c8c2462eba224 completed May 2, 2026, 7:33 p.m.
Created at: April 21, 2026, 1:58 p.m.