Triple
T31266372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesse Stone series |
E797261
|
entity |
| Predicate | subsequentAuthor |
P171523
|
FINISHED |
| Object | Michael Brandman |
—
|
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: Michael Brandman | Statement: [Jesse Stone series, subsequentAuthor, Michael Brandman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentAuthor Context triple: [Jesse Stone series, subsequentAuthor, Michael Brandman]
-
A.
authorOfPreviousWork
Indicates that one entity is the creator or writer of an earlier work referenced or built upon by another entity.
-
B.
subsequentPublication
Indicates that one publication was released after another in time, making it a later or follow-up work relative to the first.
-
C.
sequelCoAuthor
Indicates that an entity is a co-author of a sequel work related to another entity.
-
D.
subsequentAuthority
Indicates that one authority or decision follows and is derived from, or dependent on, a prior authority or decision in a sequence.
-
E.
authorLaterBecame
Indicates that the subject, who is an author of something, subsequently took on or transitioned into the role or status specified by the object at a later time.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:12 p.m.