Triple
T24679315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adirondack Regional Airport |
E611079
|
entity |
| Predicate | hasScheduledAirService |
P71580
|
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: [Adirondack Regional Airport, hasScheduledAirService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScheduledAirService Context triple: [Adirondack Regional Airport, hasScheduledAirService, 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.
hasPassengerAirlineService
chosen
Indicates that a location or facility is served by scheduled passenger airline flights.
-
C.
airSupportPlannedFrom
Indicates that air support operations are scheduled or intended to be provided starting from a specified source or location.
-
D.
inFlightService
Indicates that a service or activity is being provided to passengers during a flight.
-
E.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:08 a.m.