Triple
T26980278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian civil aviation network |
E679582
|
entity |
| Predicate | airportOwnershipModel |
P169557
|
FINISHED |
| Object | public sector airports |
—
|
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 sector airports | Statement: [Indian civil aviation network, airportOwnershipModel, public sector airports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportOwnershipModel Context triple: [Indian civil aviation network, airportOwnershipModel, public sector airports]
-
A.
airportOwner
Indicates that one entity owns, controls, or holds primary legal responsibility for an airport.
-
B.
operatorHeadquartersAirport
Indicates that the specified airport serves as the primary headquarters location for the operator.
-
C.
servesAsPrimaryAirportOperatorForCity
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
-
D.
airportDesignation
Indicates that an entity is officially designated or classified as an airport.
-
E.
airportOfficialName
Indicates the officially designated full name of an airport as recognized by authorities or governing bodies.
- F. None of above. chosen
Provenance (4 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 27, 2026, 6:45 a.m.