Triple
T3205760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Lanka Standard Time |
E67156
|
entity |
| Predicate | observesSameTimeAllYear |
P13686
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sri Lanka Standard Time, observesSameTimeAllYear, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesSameTimeAllYear Context triple: [Sri Lanka Standard Time, observesSameTimeAllYear, true]
-
A.
observesSameTimeAs
Indicates that two observation events occur simultaneously or during the same time interval.
-
B.
observesAllYear
Indicates that the observing entity continuously observes or monitors the target entity throughout the entire year without interruption.
-
C.
sameUTCOffsetAs
Indicates that two time-related entities share the same offset from Coordinated Universal Time (UTC), regardless of their specific time zones or locations.
-
D.
hasNoSeasonalClockChanges
chosen
Indicates that a place or system does not adjust its clocks for seasonal time changes such as daylight saving time.
-
E.
isSummerTimeVariantOf
Indicates that one temporal or time-related entity is the daylight-saving (summer time) version of another standard-time entity.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa559848819082d1e61f586278dd |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.