Triple
T36914695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGPD |
E913012
|
entity |
| Predicate | associatedAirportDaylightSavingTimeZone |
P34626
|
FINISHED |
| Object | BST |
—
|
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: BST | Statement: [EGPD, associatedAirportDaylightSavingTimeZone, BST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirportDaylightSavingTimeZone Context triple: [EGPD, associatedAirportDaylightSavingTimeZone, BST]
-
A.
airportTimeZone
chosen
Indicates the time zone in which an airport is located or operates.
-
B.
relatedTimeZone
Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
-
C.
timeZoneDeparture
Indicates the time zone in which the departure event occurs or is scheduled.
-
D.
capitalTimeZoneOf
Indicates that a specified time zone is the primary or official time zone in which a given capital city is located or operates.
-
E.
associatedAirportICAOSubregion
Indicates a relationship where an airport is linked to the specific ICAO-defined subregion in which it is located or with which it is operationally associated.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.