Triple
T34815678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales of Suspense #79 |
E1003626
|
entity |
| Predicate | precedesIssue |
P194034
|
FINISHED |
| Object | Tales of Suspense #80 |
—
|
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 #80 | Statement: [Tales of Suspense #79, precedesIssue, Tales of Suspense #80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesIssue Context triple: [Tales of Suspense #79, precedesIssue, Tales of Suspense #80]
-
A.
precedesDisc
Indicates that one discourse segment or unit occurs before another in the sequence of discourse.
-
B.
precedesInStability
Indicates that one entity is more stable than another, coming earlier in an ordering based on stability.
-
C.
precedesInPublication
chosen
Indicates that one item is published or released before another in a temporal or sequential order.
-
D.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
E.
startsInIssue
Indicates that an event, process, or condition begins within the context or scope of a particular issue.
- 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_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 3:59 p.m.