Triple
T26593767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malda Airport |
E667430
|
entity |
| Predicate | hasNoScheduledFlights |
P195123
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Malda Airport, hasNoScheduledFlights, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoScheduledFlights Context triple: [Malda Airport, hasNoScheduledFlights, true]
-
A.
hasScheduledFlights
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
B.
wasPlannedToFlyOn
Indicates that an entity was scheduled or intended to travel on a particular flight or aircraft.
-
C.
hasDepartureTo
Indicates that a departure event originates from one place and is directed toward a specific destination.
-
D.
hasNoAirport
Indicates that a place or region does not contain or is not served by any airport.
-
E.
airportHasScheduledPassengerService
Indicates that an airport offers regularly scheduled passenger flight services as part of its operations.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
| PDg | Predicate description generation | batch_69fda945e1e08190bf923fcd4d2c548a |
completed | May 8, 2026, 9:13 a.m. |
Created at: April 27, 2026, 2:09 a.m.