Triple
T32932967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin W. Dixon |
E842445
|
entity |
| Predicate | creditedAsAuthorOn |
P109842
|
FINISHED |
| Object | Hardy Boys book covers |
—
|
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: Hardy Boys book covers | Statement: [Franklin W. Dixon, creditedAsAuthorOn, Hardy Boys book covers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditedAsAuthorOn Context triple: [Franklin W. Dixon, creditedAsAuthorOn, Hardy Boys book covers]
-
A.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
B.
hasAuthorOf
Indicates that one entity is the author or creator of another entity (such as a work, document, or publication).
-
C.
hasAuthorOfKeyWork
Indicates that an entity serves as the author or creator of a significant or primary work associated with another entity.
-
D.
authorshipEvidence
Indicates evidence or justification supporting a claim that one entity is the author or creator of another.
-
E.
usedAsAuthorCitationFor
chosen
Indicates that one entity is cited or referenced as the author in the bibliographic citation of another 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d10722e88190bb59c5768ce23d43 |
completed | May 3, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.