Triple
T8763560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Learn the Hard Way |
E208265
|
entity |
| Predicate | yearAssociatedWithFilm |
P18082
|
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: [Learn the Hard Way, yearAssociatedWithFilm, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearAssociatedWithFilm Context triple: [Learn the Hard Way, yearAssociatedWithFilm, 2011]
-
A.
associatedWithYearFilm
Indicates a relationship where something (such as an event, award, or record) is linked to or pertains to a specific film released or identified in a given year.
-
B.
yearOfFilmAppearance
chosen
Indicates the specific year in which a film appearance by an entity took place.
-
C.
filmReleaseYear
Indicates the calendar year in which a film was first officially released to the public.
-
D.
filmAssociatedWith
Indicates a general relationship or connection between a film and another entity, such as a person, organization, event, or work.
-
E.
yearCast
Indicates the specific year in which a particular cast or casting of something (such as a film, show, or performance) took place.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dfdef9881908a7f079d87e8e338 |
completed | March 31, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.