Triple
T16854283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Video Multiple Ad Playlist |
E409746
|
entity |
| Predicate | timeOffsetValues |
P12851
|
FINISHED |
| Object | start |
—
|
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: start | Statement: [Video Multiple Ad Playlist, timeOffsetValues, start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOffsetValues Context triple: [Video Multiple Ad Playlist, timeOffsetValues, start]
-
A.
timeOffsetType
Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
-
B.
timeOffsetReference
chosen
Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
-
C.
timeOffsetInHours
Indicates the temporal difference between two time points or events, measured in hours.
-
D.
hasTimeOffset
Indicates that one temporal value is shifted or displaced from another by a specified amount of time.
-
E.
typicalUtcOffsetRange
Indicates the usual range of UTC time offsets during which an entity (such as a place or time zone) normally operates, accounting for standard and daylight saving variations.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37c6e808190975b14b228253029 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.