Triple
T34815679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales of Suspense #79 |
E1003626
|
entity |
| Predicate | followsIssue |
P134
|
FINISHED |
| Object | Tales of Suspense #78 |
—
|
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: Tales of Suspense #78 | Statement: [Tales of Suspense #79, followsIssue, Tales of Suspense #78]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsIssue Context triple: [Tales of Suspense #79, followsIssue, Tales of Suspense #78]
-
A.
followsUp
Indicates that one entity continues, responds to, or builds upon a previous entity, typically as a subsequent action, communication, or step.
-
B.
follows
chosen
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
C.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
D.
startsInIssue
Indicates that an event, process, or condition begins within the context or scope of a particular issue.
-
E.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 3, 2026, 3:59 p.m.