Triple
T31309576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howl |
E798425
|
entity |
| Predicate | firstPublicReadingDate |
P207402
|
FINISHED |
| Object | 1955-10-07 |
—
|
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: 1955-10-07 | Statement: [Howl, firstPublicReadingDate, 1955-10-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublicReadingDate Context triple: [Howl, firstPublicReadingDate, 1955-10-07]
-
A.
firstPublicReadingBy
Indicates that the referenced public reading event was the first one conducted by the specified agent (such as a person or organization).
-
B.
firstPublicReadingPlace
Indicates the location where a work, text, or piece was first publicly read or performed before an audience.
-
C.
firstBookPublicationDate
Indicates the calendar date on which an entity’s first book was officially published.
-
D.
firstBookApproxDate
Indicates an approximate date associated with when an entity’s first book was created, published, or became known.
-
E.
firstEditionStartDate
Indicates the date on which the first edition of something (such as a work, product, or event series) was initially released or began.
- F. None of above. chosen
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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:15 p.m.