Triple
T29164576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Killing Hour |
E739278
|
entity |
| Predicate | hasAuthorStatus |
P109111
|
FINISHED |
| Object | bestselling author |
—
|
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: bestselling author | Statement: [The Killing Hour, hasAuthorStatus, bestselling author]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorStatus Context triple: [The Killing Hour, hasAuthorStatus, bestselling author]
-
A.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
B.
authorshipStatus
Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
-
C.
authorStatus
chosen
Indicates the role or standing an individual holds as an author, such as their level of contribution, recognition, or current authorship state in relation to a work.
-
D.
hasDebutStatusForAuthor
Indicates that an author’s work or appearance is identified as their first (debut) instance in a given context.
-
E.
hasAuthorOf
Indicates that one entity is the author or creator of another entity (such as a work, document, or 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 11:49 a.m.