Triple
T28640924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delilah S. Dawson |
E724918
|
entity |
| Predicate | hasWrittenComicsFor |
P78982
|
FINISHED |
| Object | Marvel Comics |
—
|
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: Marvel Comics | Statement: [Delilah S. Dawson, hasWrittenComicsFor, Marvel Comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWrittenComicsFor Context triple: [Delilah S. Dawson, hasWrittenComicsFor, Marvel Comics]
-
A.
wroteComicSeries
Indicates that an entity is the author or primary writer responsible for creating a particular comic series.
-
B.
hasComicSeries
Indicates that one entity is the comic series to which another entity belongs or with which it is associated.
-
C.
workWrittenFor
Indicates that a creative work was specifically composed, produced, or created for a particular person, group, event, purpose, or medium.
-
D.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
E.
hasWrittenFiction
chosen
Indicates that one entity is the creator or author of fictional written works associated with another entity.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:44 a.m.