Triple
T8501404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go Set a Watchman |
E201224
|
entity |
| Predicate | preorderSales |
P83075
|
FINISHED |
| Object | record-breaking for HarperCollins |
—
|
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: record-breaking for HarperCollins | Statement: [Go Set a Watchman, preorderSales, record-breaking for HarperCollins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preorderSales Context triple: [Go Set a Watchman, preorderSales, record-breaking for HarperCollins]
-
A.
saleType
Indicates the specific category or method by which a sale is conducted or classified (e.g., retail, wholesale, auction).
-
B.
saleTo
Indicates a transaction in which one party sells goods, services, or assets to another party.
-
C.
soldProducts
Indicates that an entity has sold certain products to another entity or in a particular context.
-
D.
ordersBy
Indicates that one entity arranges, sorts, or sequences another entity according to a specified criterion or set of criteria.
-
E.
subsequentPlanBySeller
Indicates that a seller initiates or proposes a follow-up plan or action after an earlier plan or event.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe59ad65c8190a2b8e6d22269853a |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:14 p.m.