Triple
T31515804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiffany Quilkin |
E804071
|
entity |
| Predicate | originalWorkCreators |
P154484
|
FINISHED |
| Object | Brian K. Vaughan |
—
|
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: Brian K. Vaughan | Statement: [Tiffany Quilkin, originalWorkCreators, Brian K. Vaughan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalWorkCreators Context triple: [Tiffany Quilkin, originalWorkCreators, Brian K. Vaughan]
-
A.
authorWorkCreator
Indicates that an entity is the creator (author) responsible for producing a particular work.
-
B.
originalWorkBy
chosen
Indicates that one entity is the creator or originator of another entity (such as a work, idea, or product).
-
C.
relatedWorkCreator
Indicates that the creator of one work is related (e.g., by authorship, contribution, or collaboration) to the creation of another work.
-
D.
composerOfSourceWork
Indicates that an entity is the composer who created the original source work on which another work is based.
-
E.
publisherOfOriginalWorks
Indicates that an entity serves as the publisher responsible for releasing the original versions of certain works.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00d15f7b788190a3bf440be7837192 |
completed | May 10, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_6a00d0f8ef548190b1c15b06164eec4a |
completed | May 10, 2026, 6:39 p.m. |
Created at: April 30, 2026, 9:53 p.m.