Triple
T35014423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Judas Contract |
E1010014
|
entity |
| Predicate | storyArcStartIssue |
P163477
|
FINISHED |
| Object | Tales of the Teen Titans #42 |
—
|
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 the Teen Titans #42 | Statement: [The Judas Contract, storyArcStartIssue, Tales of the Teen Titans #42]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyArcStartIssue Context triple: [The Judas Contract, storyArcStartIssue, Tales of the Teen Titans #42]
-
A.
storyArcStart
chosen
Indicates the point in a narrative where a particular story arc or plotline begins.
-
B.
startsInIssue
Indicates that an event, process, or condition begins within the context or scope of a particular issue.
-
C.
startIssue
Indicates initiating or opening an issue, ticket, or problem report within a tracking or management process.
-
D.
storyArcLength
Indicates the duration or extent of a narrative arc within a story, such as how long a particular plotline continues.
-
E.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.