Triple
T10366703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Actually (film score) |
E244266
|
entity |
| Predicate | associatedYearOfFilm |
P13249
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Love Actually (film score), associatedYearOfFilm, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedYearOfFilm Context triple: [Love Actually (film score), associatedYearOfFilm, 2003]
-
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
Indicates the specific year in which a film appearance by an entity took place.
-
C.
filmReleaseYear
chosen
Indicates the calendar year in which a film was first officially released to the public.
-
D.
playedInYear
Indicates that an entity participated in or was active in a particular activity, event, or role during a specified calendar year.
-
E.
relatedYear
Indicates a connection between an entity and a specific year that is relevant to its occurrence, validity, or significance.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e96fd6f081908f630a16106996d9 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, noon