Triple
T35245206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loaded |
E1017639
|
entity |
| Predicate | originalAMCPremiereDate |
—
|
GENERATED |
| Object | 2017-07-17 |
—
|
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: originalAMCPremiereDate Context triple: [Loaded, originalAMCPremiereDate, 2017-07-17]
-
A.
revisedPremiereDate
Indicates that the originally scheduled premiere date of something has been changed to a new date.
-
B.
premieredOn
chosen
Indicates that an event, work, or production had its first public showing or debut on a specified date or at a specified time.
-
C.
premieredWith
Indicates that one entity made its first public debut or initial showing together with another entity, at the same time or in the same event.
-
D.
revisedVersionPremiereDate
Indicates the date on which a revised version of a work was first publicly premiered or released.
-
E.
timePeriodOfPremiere
Indicates the time period during which the premiere of something (such as a work, event, or performance) took place.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.