Triple
T37694578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FGSL |
E938892
|
entity |
| Predicate | associatedAirportUTCOffset |
P58803
|
FINISHED |
| Object | +01: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: +01:00 | Statement: [FGSL, associatedAirportUTCOffset, +01:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirportUTCOffset Context triple: [FGSL, associatedAirportUTCOffset, +01:00]
-
A.
airportTimeZone
Indicates the time zone in which an airport is located or operates.
-
B.
timeZoneDeparture
Indicates the time zone in which the departure event occurs or is scheduled.
-
C.
associatedAirport
chosen
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
-
D.
countryMainlandTimeDifference
Indicates the time difference between a country’s mainland and another referenced region or standard time.
-
E.
associatedAirportReplaced
Indicates that one airport in an association has been superseded or replaced by another airport.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.