Triple
T17700647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TJT |
E441288
|
entity |
| Predicate | hasFixedUTCOffset |
P4886
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TJT, hasFixedUTCOffset, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFixedUTCOffset Context triple: [TJT, hasFixedUTCOffset, yes]
-
A.
isFixedOffsetFromUTC
chosen
Indicates that one time-related entity consistently differs from Coordinated Universal Time (UTC) by a specific, unchanging offset.
-
B.
isFixedOffsetSince
Indicates that one entity consistently occurs or is positioned at a constant, unchanging offset in time or value relative to another reference entity.
-
C.
hasStandardTimeUTCOffset
Indicates the fixed difference in hours and minutes between an entity’s standard (non-daylight-saving) local time and Coordinated Universal Time (UTC).
-
D.
hasTimeOffset
Indicates that one temporal value is shifted or displaced from another by a specified amount of time.
-
E.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715ae1fc81908438a1bba970c6ec |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:04 a.m.