Triple
T31734831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection Men |
E809963
|
entity |
| Predicate | hasSeriesPredecessor |
P13316
|
FINISHED |
| Object | The Falls |
—
|
NE NERFINISHED |
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 Falls | Statement: [Resurrection Men, hasSeriesPredecessor, The Falls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeriesPredecessor Context triple: [Resurrection Men, hasSeriesPredecessor, The Falls]
-
A.
isPrequelTo
Indicates that one work or event occurs earlier in time and narratively sets up or leads into another work or event.
-
B.
predecessorSeries
chosen
Indicates that one series directly precedes another in an ordered sequence or lineage.
-
C.
precedesInFranchise
Indicates that one installment in a franchise comes before another in the franchise’s canonical or release order.
-
D.
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.
-
E.
hasFictionalSuccessor
Indicates that one entity is followed or replaced by another entity within a fictional or narrative context.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: April 30, 2026, 11:23 p.m.