Triple

T6894717
Position Surface form Disambiguated ID Type / Status
Subject Changsha Huanghua International Airport E159141 entity
Predicate hasDomesticNetwork P1658 FINISHED
Object extensive 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: extensive | Statement: [Changsha Huanghua International Airport, hasDomesticNetwork, extensive]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDomesticNetwork
Context triple: [Changsha Huanghua International Airport, hasDomesticNetwork, extensive]
  • A. hasDomesticTerminal
    Indicates that a transportation facility, typically an airport, includes a terminal dedicated to domestic (within-country) travel operations.
  • B. hasNetworkUS
    Indicates that an entity possesses, operates, or is associated with a network located in or serving the United States.
  • C. connectedToNationalNetworkAt
    Indicates that an entity has a direct linkage or access point to a broader national-level network or infrastructure.
  • D. hasDomesticFlights chosen
    Indicates that an airline or airport operates flights within the same country, connecting domestic destinations.
  • E. hasDomesticConcourse
    Indicates that a transportation facility includes a concourse area designated for domestic (within-country) passengers or services.
  • 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_69c6883568c8819081db6407e892cccc completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d933032c8190997d67a15897619b completed March 27, 2026, 7:23 p.m.
PD Predicate disambiguation batch_69c6d7b7681481909ec50509b19fcf81 completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:24 p.m.