Triple
T289311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Origin of Species |
E5954
|
entity |
| Predicate | firstEditionPublicationDate |
P4114
|
FINISHED |
| Object | 24 November 1859 |
—
|
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: 24 November 1859 | Statement: [On the Origin of Species, firstEditionPublicationDate, 24 November 1859]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionPublicationDate Context triple: [On the Origin of Species, firstEditionPublicationDate, 24 November 1859]
-
A.
firstEditionSoldOutTime
Indicates the point in time at which the first edition of an item became completely sold out.
-
B.
firstPublisher
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
C.
firstEditionPrintRun
Indicates the initial quantity of copies produced when a work is printed in its first published edition.
-
D.
firstAppeared
chosen
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
E.
firstEditionHeldIn
Indicates the location where the first edition or initial occurrence of an event was held.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e4df5508190ab75115ac6b3964e |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7d089081909810442c3d0182f6 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.