Triple

T14521799
Position Surface form Disambiguated ID Type / Status
Subject HCMM E340669 entity
Predicate associatedAirportFunction P50462 FINISHED
Object civil aviation 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: civil aviation | Statement: [HCMM, associatedAirportFunction, civil aviation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedAirportFunction
Context triple: [HCMM, associatedAirportFunction, civil aviation]
  • A. hasAirportRelatedFunction chosen
    Indicates that something performs a role, service, or activity specifically related to the operation, support, or functioning of an airport.
  • B. associatedAirportServes
    Indicates that a given airport provides service to, or is used by, the associated entity (such as a city, region, or facility).
  • C. associatedAirport
    Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
  • D. 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.
  • E. associatedWithAirportType
    Indicates that an entity has a connection or linkage to a specific category or type of airport.
  • 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_69d822dac79c8190a84a073f3cbaced5 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69de9a72cff08190878b4bed9b0b5eb5 completed April 14, 2026, 7:50 p.m.
PD Predicate disambiguation batch_69de5c518fc08190a6ce4d8be05c4c5d completed April 14, 2026, 3:25 p.m.
Created at: April 10, 2026, 1:22 a.m.