Triple
T7595149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toy Story Toons |
E179839
|
entity |
| Predicate | firstShortReleaseYear |
P10224
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Toy Story Toons, firstShortReleaseYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstShortReleaseYear Context triple: [Toy Story Toons, firstShortReleaseYear, 2011]
-
A.
firstVersionYear
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
B.
firstCommercialReleaseYear
Indicates the calendar year in which something (such as a product, work, or service) was first made commercially available to the public.
-
C.
firstSeriesYear
chosen
Indicates the year in which a series (such as a TV show, book series, or sports league season) first began or was initially released.
-
D.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
E.
firstGenerationReleaseDate
Indicates the calendar date on which the first generation or initial version of something was officially released.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9bbcd8081909a229d7faa2ffdc8 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.