Triple
T2350501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memento |
E47435
|
entity |
| Predicate | isInChristopherNolanFilmography |
P15620
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Memento, isInChristopherNolanFilmography, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInChristopherNolanFilmography Context triple: [Memento, isInChristopherNolanFilmography, true]
-
A.
includedInFilm
Indicates that one entity (such as a scene, segment, or element) is contained within or forms part of a particular film.
-
B.
partOfFilmographyOf
chosen
Indicates that a work (such as a film, show, or role) is included in the body of screen-related works credited to a particular person.
-
C.
hasNotableFilm
Indicates that an entity is associated with a film that is considered significant, well-known, or particularly noteworthy.
-
D.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
E.
producedFilm
Indicates that one entity served as the producer (or production company) responsible for making or financing the creation of a particular film.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abcb802da08190980100444010f91e |
completed | March 7, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69abc5981ce48190a3f7852d28276e11 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:54 p.m.