Triple
T2668042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion Pictures |
E55683
|
entity |
| Predicate | relaunch |
P41560
|
FINISHED |
| Object | 2013 relaunch under MGM |
—
|
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: 2013 relaunch under MGM | Statement: [Orion Pictures, relaunch, 2013 relaunch under MGM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relaunch Context triple: [Orion Pictures, relaunch, 2013 relaunch under MGM]
-
A.
rebootOf
Indicates that one work is a new version that restarts or reimagines the story, continuity, or franchise of another earlier work.
-
B.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
C.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
-
D.
recommissioned
Indicates that something previously deactivated, retired, or out of service has been restored and formally returned to active use or operation.
-
E.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd98a4ee88190aa7ef914e316ba31 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8f98c348190a68064c565589459 |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:54 p.m.