Triple
T2324542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solomon Islands Time |
E48256
|
entity |
| Predicate | followsCoordinatedUniversalTime |
P9276
|
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: [Solomon Islands Time, followsCoordinatedUniversalTime, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsCoordinatedUniversalTime Context triple: [Solomon Islands Time, followsCoordinatedUniversalTime, yes]
-
A.
relationToUTC
chosen
Indicates the temporal offset or correspondence between a given time value and Coordinated Universal Time (UTC).
-
B.
sameUTCOffsetAs
Indicates that two time-related entities share the same offset from Coordinated Universal Time (UTC), regardless of their specific time zones or locations.
-
C.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
-
D.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
E.
followedByTimeZone
Indicates that one time zone chronologically succeeds another in a defined ordering or sequence.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:50 p.m.