Triple
T8501390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go Set a Watchman |
E201224
|
entity |
| Predicate | firstPrintRun |
P3998
|
FINISHED |
| Object | 2 million copies |
—
|
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: 2 million copies | Statement: [Go Set a Watchman, firstPrintRun, 2 million copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPrintRun Context triple: [Go Set a Watchman, firstPrintRun, 2 million copies]
-
A.
firstEditionPrintRun
chosen
Indicates the initial quantity of copies produced when a work is printed in its first published edition.
-
B.
printedFirstEditionOf
Indicates that the subject entity produced and issued the initial published edition of the object entity.
-
C.
firstPrintedInPlace
Indicates the place where an item (such as a work or edition) was first printed.
-
D.
printRun
Indicates the number or instance of times a particular item or edition has been printed or produced.
-
E.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
- 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_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. |
Created at: March 30, 2026, 6:14 p.m.