Triple
T38390578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Universe |
E899704
|
entity |
| Predicate | firstReleasedFilm |
P140739
|
FINISHED |
| Object | The Mummy (2017 film) |
E506671
|
NE 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: The Mummy (2017 film) | Statement: [Dark Universe, firstReleasedFilm, The Mummy (2017 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstReleasedFilm Context triple: [Dark Universe, firstReleasedFilm, The Mummy (2017 film)]
-
A.
firstFeatureFilmRelease
Indicates the date or event of an entity’s debut feature-length film being publicly released.
-
B.
hasFirstFilm
chosen
Indicates the specific film that is recognized as the first film associated with an entity (such as a person, series, or franchise).
-
C.
firstFilmTitle
Indicates the title of the first film associated with a given entity.
-
D.
firstAppearanceFilm
Indicates the film in which an entity (such as a character or person) makes its first on-screen appearance.
-
E.
firstUsedInFeatureFilm
Indicates that something (such as a technique, character, or element) made its earliest appearance or application in a particular feature film.
- F. None of above.
Provenance (4 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_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41cc9d45cc8190b50d2fffdbef2371 |
completed | June 29, 2026, 1:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.