Triple
T10755860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KLGC |
E253691
|
entity |
| Predicate | subjectAirportOwnership |
P34625
|
FINISHED |
| Object | public |
—
|
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: public | Statement: [KLGC, subjectAirportOwnership, public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectAirportOwnership Context triple: [KLGC, subjectAirportOwnership, public]
-
A.
airportOwner
chosen
Indicates that one entity owns, controls, or holds primary legal responsibility for an airport.
-
B.
airlineOwnershipType
Indicates the type or nature of ownership relationship that exists between an airline and its owning entity.
-
C.
belongsToAirportSystem
Indicates that an airport is a member or component of a specific airport system or network.
-
D.
belongsToAirport
Indicates that one entity is part of, associated with, or under the jurisdiction of a specific airport.
-
E.
parentAirport
Indicates that one airport serves as the primary or overarching facility from which another, subsidiary or associated airport is derived or managed.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d72e9e224c819099d16aba77322812 |
completed | April 9, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.