Triple
T8070216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAT |
E188350
|
entity |
| Predicate | associatedAirportDST |
P34626
|
FINISHED |
| Object | UTC−07:00 |
—
|
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: UTC−07:00 | Statement: [FAT, associatedAirportDST, UTC−07:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirportDST Context triple: [FAT, associatedAirportDST, UTC−07:00]
-
A.
associatedAirport
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
-
B.
associatedAirportServes
Indicates that a given airport provides service to, or is used by, the associated entity (such as a city, region, or facility).
-
C.
airportTimeZone
chosen
Indicates the time zone in which an airport is located or operates.
-
D.
typicalDestinationAirportIATA
Indicates the IATA airport code that is typically the destination in this kind of trip or route.
-
E.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ffe29188190834ec4f71043a99d |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:27 p.m.