Triple
T38390572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Universe |
E899704
|
entity |
| Predicate | plannedFilm |
P140678
|
FINISHED |
| Object | The Mummy (2017 film) |
—
|
NE NERFINISHED |
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: The Mummy (2017 film) | Statement: [Dark Universe, plannedFilm, The Mummy (2017 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedFilm Context triple: [Dark Universe, plannedFilm, The Mummy (2017 film)]
-
A.
filmProject
chosen
Indicates a relationship where an entity is involved in or associated with a specific film production project.
-
B.
filmRelease
Indicates the event or relationship in which a film is made publicly available, typically specifying when, where, or how it is released.
-
C.
producedFilm
Indicates that one entity served as the producer (or production company) responsible for making or financing the creation of a particular film.
-
D.
filmAdaptationAnnounced
Indicates that an official announcement has been made that a film adaptation of a work (such as a book, game, or other source material) will be produced.
-
E.
filmMovement
Indicates the cinematic movement or stylistic school with which a film is associated.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:31 p.m.