Triple
T37317818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonight |
E926383
|
entity |
| Predicate | hasReleaseSchedule |
—
|
GENERATED |
| Object | weekly |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleaseSchedule Context triple: [Tonight, hasReleaseSchedule, weekly]
-
A.
hasScheduledReleases
Indicates that an entity has one or more releases planned to occur at specific future times.
-
B.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
C.
releaseSchedule
chosen
Indicates the planned timing and sequence for when something (such as a product, update, or content) will be made available or launched.
-
D.
hasReleased
Indicates that an entity has made another entity publicly available or officially launched it.
-
E.
intendedForReleaseIn
Indicates that something is planned or scheduled to be made available or launched within a specified context, such as a time, market, or platform.
- F. None of above.
Provenance (1 batch)
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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.