Triple
T34980548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Road to Paradise |
E1008800
|
entity |
| Predicate | literaryPrequelSeries |
P47760
|
FINISHED |
| Object | Road to Perdition |
—
|
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: Road to Perdition | Statement: [Road to Paradise, literaryPrequelSeries, Road to Perdition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryPrequelSeries Context triple: [Road to Paradise, literaryPrequelSeries, Road to Perdition]
-
A.
prequelOrSequelTo
Indicates that one work in a narrative series occurs earlier or later in the storyline or release order relative to another work, as its prequel or sequel.
-
B.
isPrequelTo
chosen
Indicates that one work or event occurs earlier in time and narratively sets up or leads into another work or event.
-
C.
literarySeries
Indicates that one work is part of, or belongs to, a larger literary series that connects multiple related works.
-
D.
hasSequelInCanon
Indicates that a work has a subsequent work that continues its story within the officially recognized continuity.
-
E.
literaryPredecessor
Indicates that one work of literature precedes and influences another in a historically or artistically significant way.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:01 p.m.