Triple
T14150438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Begumpet Airport |
E350663
|
entity |
| Predicate | ceasedCommercialOperations |
P17360
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Begumpet Airport, ceasedCommercialOperations, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedCommercialOperations Context triple: [Begumpet Airport, ceasedCommercialOperations, 2008]
-
A.
operatedUntil
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
B.
ceasedOperation
chosen
Indicates that an entity has stopped functioning, operating, or carrying out its activities, typically in a permanent or indefinite manner.
-
C.
ceasedOperationsAs
Indicates that an entity stopped functioning or operating in a particular role, capacity, or status.
-
D.
closedAsIndependentCompany
Indicates that an entity has ceased operations as an independent company, typically due to closure, merger, or acquisition.
-
E.
ceasedOperationAfter
Indicates that one entity stopped functioning, operating, or being active after another specified event or entity’s operation ended.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6124e23481909e5132a40a1d8624 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:56 a.m.