Triple
T28519860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Brautigan |
E721729
|
entity |
| Predicate | bookPublicationContext |
P134199
|
FINISHED |
| Object | Hearts in Atlantis (1999) |
—
|
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: Hearts in Atlantis (1999) | Statement: [Ted Brautigan, bookPublicationContext, Hearts in Atlantis (1999)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookPublicationContext Context triple: [Ted Brautigan, bookPublicationContext, Hearts in Atlantis (1999)]
-
A.
contextOfPublication
Indicates the contextual circumstances (such as venue, medium, or setting) in which a work or content is published.
-
B.
bookContext
chosen
Indicates that something is relevant to, derived from, or situated within the context or setting of a particular book.
-
C.
bookPublicationInUniverse
Indicates that a book is published or exists within a specific fictional or narrative universe.
-
D.
publicationAbout
Indicates that a publication has content whose subject or focus is the referenced entity.
-
E.
workPublishedBy
Indicates that a work (such as a book, article, or other creation) has been issued or made publicly available by a particular publisher or publishing entity.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fa169e48190b061b3b3014a079d |
completed | May 2, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:19 a.m.