Triple
T26537945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJOA |
E671300
|
entity |
| Predicate | airportUTCoffset |
P712
|
FINISHED |
| Object | +09: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: +09:00 | Statement: [RJOA, airportUTCoffset, +09:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportUTCoffset Context triple: [RJOA, airportUTCoffset, +09:00]
-
A.
hoursAheadOfUTC
Indicates the number of hours by which a given time or timezone is offset ahead of Coordinated Universal Time (UTC).
-
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.
timeOffsetInHours
Indicates the temporal difference between two time points or events, measured in hours.
-
D.
countryMainlandTimeDifference
Indicates the time difference between a country’s mainland and another referenced region or standard time.
-
E.
airportTimeZone
Indicates the time zone in which an airport is located or operates.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 1:39 a.m.