Triple
T8841535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomorrowland |
E210398
|
entity |
| Predicate | hasAfterMovie |
P84950
|
FINISHED |
| Object | Tomorrowland official aftermovie |
—
|
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: Tomorrowland official aftermovie | Statement: [Tomorrowland, hasAfterMovie, Tomorrowland official aftermovie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAfterMovie Context triple: [Tomorrowland, hasAfterMovie, Tomorrowland official aftermovie]
-
A.
hasSequel
Indicates that one work is followed by another work that continues its story, timeline, or thematic development.
-
B.
endedWithFilm
Indicates that an event, series, or process concluded with the showing, release, or occurrence of a particular film.
-
C.
statusAfterFirstFilm
Indicates the status or condition of an entity immediately following the release or completion of its first film.
-
D.
hasPostCreditsScene
Indicates that a film or episode includes a scene that appears during or after the closing credits.
-
E.
hasSequelType
Indicates that one work has a sequel of a specified type or category in relation to another work.
- F. None of above. chosen
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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60876c6c8190b1b490e447e1cf4b |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:48 p.m.