Triple
T21560515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrtle |
E532007
|
entity |
| Predicate | publicationOfWorkAppearedIn |
P309
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Myrtle, publicationOfWorkAppearedIn, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationOfWorkAppearedIn Context triple: [Myrtle, publicationOfWorkAppearedIn, 1961]
-
A.
publicationOfWork
Indicates that a particular work has been formally made public, typically through printing, distribution, or release by a publisher or similar entity.
-
B.
publishedWorksBy
Indicates that one entity has created works that have been made publicly available by another entity (such as an author’s works published by a publisher).
-
C.
publishedIn
chosen
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
D.
appearsInPublication
Indicates that an entity is featured, mentioned, or discussed within a specific publication.
-
E.
publicationMention
Indicates that one entity (such as a document, statement, or record) explicitly references or cites a particular publication.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e2db2c81908b965312c50d4354 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.