Triple
T8070217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAT |
E188350
|
entity |
| Predicate | associatedAirportStandardTimeOffset |
P712
|
FINISHED |
| Object | UTC−08: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−08:00 | Statement: [FAT, associatedAirportStandardTimeOffset, UTC−08:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirportStandardTimeOffset Context triple: [FAT, associatedAirportStandardTimeOffset, UTC−08:00]
-
A.
airportTimeZone
Indicates the time zone in which an airport is located or operates.
-
B.
UTCOffsetStandardTime
chosen
Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
-
C.
capitalTimeZoneOf
Indicates that a specified time zone is the primary or official time zone in which a given capital city is located or operates.
-
D.
offsetFromAtlanticStandardTime
Indicates the time difference, in hours or minutes, between a given time reference and Atlantic Standard Time.
-
E.
timeZoneDestination
Indicates the time zone associated with the destination location in a given context or event.
- 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.