Triple
T21940614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRT |
E541808
|
entity |
| Predicate | dstVariantOffset |
P128586
|
FINISHED |
| Object | UTC−02: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: UTC−02:00 | Statement: [BRT, dstVariantOffset, UTC−02:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dstVariantOffset Context triple: [BRT, dstVariantOffset, UTC−02:00]
-
A.
dstOffsetSameAsStandard
Indicates that the daylight saving time offset is the same as the standard (non-daylight-saving) time offset.
-
B.
offsetType
Indicates the specific kind or category of offset applied in a relationship, such as how far or in what manner one value, position, or event is shifted relative to another.
-
C.
offsetValue
chosen
Indicates the numerical amount by which one value, position, or parameter is shifted or adjusted relative to a reference point.
-
D.
offsetFrom
Indicates that one entity is positioned or scheduled at a specific distance, time, or value away from another reference entity.
-
E.
usesOffsetFrom
Indicates that one entity determines or expresses its position, value, or behavior relative to another by applying a specified offset from that reference.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12420b1cc81909b375891aedc0979 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:55 p.m.