Triple
T10254860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Engines (2018 film) |
E240435
|
entity |
| Predicate | setInFuture |
P46662
|
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: [Mortal Engines (2018 film), setInFuture, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInFuture Context triple: [Mortal Engines (2018 film), setInFuture, true]
-
A.
isFutureEvent
chosen
Indicates that an event is scheduled to occur at a time later than the present moment.
-
B.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
-
C.
scheduledAfter
Indicates that one event or action is planned to occur later in time than another in a defined schedule or sequence.
-
D.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
E.
futureServes
Indicates that, at a future time, one entity will perform a service or act in a serving role for another entity.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:30 a.m.