Triple
T28135262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murderer |
E714181
|
entity |
| Predicate | hasAuthorOfSameWorkAs |
P173708
|
FINISHED |
| Object | Sleuth |
—
|
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: Sleuth | Statement: [Murderer, hasAuthorOfSameWorkAs, Sleuth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorOfSameWorkAs Context triple: [Murderer, hasAuthorOfSameWorkAs, Sleuth]
-
A.
workBySameAuthorAs
Indicates that two works share the same author, i.e., they were created by the same person or entity.
-
B.
hasAuthorOfOtherWork
Indicates that an entity is the author of another distinct work associated with the first entity.
-
C.
complementsWorkBySameAuthor
Indicates that one work enhances, completes, or supplements another work created by the same author.
-
D.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
E.
workInCollectionBySameAuthor
Indicates that one work is included in a collection whose other contents are by the same author as that work.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 27, 2026, 9:49 p.m.