Triple
T34214821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P1 |
E877754
|
entity |
| Predicate | timeShiftAvailability |
P19768
|
FINISHED |
| Object | on-demand via podcast |
—
|
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: on-demand via podcast | Statement: [P1, timeShiftAvailability, on-demand via podcast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeShiftAvailability Context triple: [P1, timeShiftAvailability, on-demand via podcast]
-
A.
timeShiftService
chosen
Indicates that a service is provided with a shifted or delayed time relative to its original or real-time schedule.
-
B.
timeShiftProperty
Indicates a relationship where one property value is derived from another by applying a temporal shift (e.g., offsetting it to an earlier or later point in time).
-
C.
shiftsWhen
Indicates that one state, condition, or configuration changes to another under specified circumstances or triggers.
-
D.
timeStatus
Indicates the temporal state or condition of an event or entity relative to a reference time (e.g., past, present, future, ongoing, or scheduled).
-
E.
availabilityPeriod
Indicates the time span during which something is available or valid for use.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107cf7f4819092ab182979eeaf45 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.