Triple
T8759010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tahiti Time |
E208145
|
entity |
| Predicate | isBehindUTCByHours |
P85229
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Tahiti Time, isBehindUTCByHours, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBehindUTCByHours Context triple: [Tahiti Time, isBehindUTCByHours, 10]
-
A.
isTwoHoursBehind
Indicates that one entity’s time zone or clock is exactly two hours earlier than another entity’s time zone or clock.
-
B.
isFourHoursBehind
Indicates that one entity’s time zone or local time is exactly four hours earlier than another reference time or time zone.
-
C.
isThreeHoursBehind
Indicates that one entity’s time zone or local time is exactly three hours earlier than another entity’s.
-
D.
hoursBehindCentralDaylightTime
Indicates how many hours a given time zone or location’s local time differs behind Central Daylight Time (CDT).
-
E.
isAheadOfUTC
Indicates that a time, date, or timezone occurs at a later (positive offset) time than Coordinated Universal Time (UTC).
- F. None of above. chosen
Provenance (4 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5df81c58819089af99306e103dbb |
completed | March 31, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:40 p.m.