Triple
T4056115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Folio of Shakespeare |
E84697
|
entity |
| Predicate | approximateOriginalPrintRun |
P12799
|
FINISHED |
| Object | about 750 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: about 750 copies | Statement: [First Folio of Shakespeare, approximateOriginalPrintRun, about 750 copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateOriginalPrintRun Context triple: [First Folio of Shakespeare, approximateOriginalPrintRun, about 750 copies]
-
A.
estimatedCopiesPrinted
chosen
Indicates the approximate number of copies of an item that have been printed.
-
B.
firstEditionPrintRun
Indicates the initial quantity of copies produced when a work is printed in its first published edition.
-
C.
originalRunStatus
Indicates the initial or prior execution state of a run before any subsequent updates or changes.
-
D.
hasEstimatedOriginalVolume
Indicates that an entity is associated with an approximate or calculated value for its original volume.
-
E.
originalRunIncluded
Indicates that an entity’s initial or primary execution, performance, or airing is contained within or forms part of another specified run or collection of runs.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbabec608190a35d39d3d03b928b |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.