Triple
T80656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Origin of Species |
E1619
|
entity |
| Predicate | firstEditionPrintRun |
P3998
|
FINISHED |
| Object | 1250 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: 1250 copies | Statement: [On the Origin of Species, firstEditionPrintRun, 1250 copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionPrintRun Context triple: [On the Origin of Species, firstEditionPrintRun, 1250 copies]
-
A.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
-
B.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
C.
firstDeployed
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
-
D.
publisherImprint
Indicates the publishing imprint or brand under which a work is issued by a publisher.
-
E.
firstDeployedFor
Indicates that an entity was initially deployed or put into operational use specifically for another entity (such as a project, mission, or organization).
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a25053ca208190a371b0d38000c2b9 |
completed | Feb. 28, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69a24eb2998c819082681da74601d446 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a25052f0b081908615878ab7d0bde1 |
completed | Feb. 28, 2026, 2:17 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.