Triple
T7139099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In the Event of My Father’s Death |
E166393
|
entity |
| Predicate | collectionPublicationType |
P218
|
FINISHED |
| Object | short story collection |
—
|
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: short story collection | Statement: [In the Event of My Father’s Death, collectionPublicationType, short story collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionPublicationType Context triple: [In the Event of My Father’s Death, collectionPublicationType, short story collection]
-
A.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
B.
publicationCollection
Indicates that one entity is a collection or grouping that contains or organizes multiple publication entities.
-
C.
publicationAbout
Indicates that a publication has content whose subject or focus is the referenced entity.
-
D.
dataPublication
Indicates that some data has been made publicly available or formally released, typically through a defined dissemination or publishing process.
-
E.
fieldOfPublication
Indicates the academic or topical area in which a work is published.
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e694cc3c81908b0d54c2496a0722 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.