Triple
T31323980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batman: Hush |
E798828
|
entity |
| Predicate | featuresRomanticSubplotBetween |
P150696
|
FINISHED |
| Object | Batman and Catwoman |
—
|
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: Batman and Catwoman | Statement: [Batman: Hush, featuresRomanticSubplotBetween, Batman and Catwoman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRomanticSubplotBetween Context triple: [Batman: Hush, featuresRomanticSubplotBetween, Batman and Catwoman]
-
A.
hasRomanticSubplot
chosen
Indicates that a work includes a secondary storyline centered on a romantic relationship between characters.
-
B.
romanticSubplotCentral
Indicates that a romantic subplot is a primary, driving element of the narrative rather than a minor or peripheral thread.
-
C.
hasRomanticPlotline
Indicates that there is a romantic storyline or relationship development present between the entities.
-
D.
hasRomanticEntanglementInPlot
Indicates that a romantic relationship or involvement between characters is a significant element within the narrative plot.
-
E.
romanticPlotFunction
Indicates a narrative relationship where characters are involved in or contribute to a romantic storyline or romantic development within the plot.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0075be7f54819081ab12bc1dab53bb |
completed | May 10, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a0073a19030819098c23faa3adcb96e |
completed | May 10, 2026, 12:01 p.m. |
Created at: April 29, 2026, 9:15 p.m.