Triple
T37713674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerry Conway |
E939403
|
entity |
| Predicate | notableEventWritten |
P148591
|
FINISHED |
| Object | Death of Gwen Stacy storyline |
E517396
|
NE 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: Death of Gwen Stacy storyline | Statement: [Gerry Conway, notableEventWritten, Death of Gwen Stacy storyline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventWritten Context triple: [Gerry Conway, notableEventWritten, Death of Gwen Stacy storyline]
-
A.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
B.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
C.
notableEventIncluded
Indicates that a particular notable event is contained within, or forms part of, a larger collection, record, or context.
-
D.
notableStoryEvent
chosen
Indicates that an event plays a significant or memorable role within the narrative or storyline associated with the subject.
-
E.
notableEventInLife
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
- F. None of above.
Provenance (4 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40cdd5cd5081909eb9b9c27be4793b |
completed | June 28, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.