Triple
T30711798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medusa |
E781913
|
entity |
| Predicate | firstPublicationDateInFiction |
P104118
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Medusa, firstPublicationDateInFiction, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublicationDateInFiction Context triple: [Medusa, firstPublicationDateInFiction, 2007]
-
A.
firstDraftPublishedIn
Indicates that the first draft of a work was published or made publicly available in a specified venue, medium, or publication.
-
B.
firstBookPublicationDate
Indicates the calendar date on which an entity’s first book was officially published.
-
C.
firstPublicationIn
Indicates the initial venue, medium, or context in which a work was first published.
-
D.
firstSerialPublicationYear
chosen
Indicates the calendar year in which a work was first published in serial form.
-
E.
workOfFictionStartDate
Indicates the date on which a work of fiction was first created, published, released, or otherwise began to exist as a distinct fictional work.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a031b40c6d0819096f4b9787a1f09d1 |
completed | May 12, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_6a03191f8ee08190b3416b044869ddfd |
completed | May 12, 2026, 12:12 p.m. |
Created at: April 29, 2026, 8:35 p.m.