Triple
T8813915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impromptus, D. 899 |
E209730
|
entity |
| Predicate | approximateYearOfFirstPublication |
P13193
|
FINISHED |
| Object | 1827 |
—
|
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: 1827 | Statement: [Impromptus, D. 899, approximateYearOfFirstPublication, 1827]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateYearOfFirstPublication Context triple: [Impromptus, D. 899, approximateYearOfFirstPublication, 1827]
-
A.
approximateStartYear
chosen
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
B.
firstCompletePublicationYear
Indicates the calendar year in which an entity’s first complete publication was released.
-
C.
firstAssociatedPublicationYear
Indicates the calendar year in which an entity’s earliest associated publication was first released or made publicly available.
-
D.
firstPublishedInWorkYear
Indicates the year in which a work was first published.
-
E.
introducedInPublicationYear
Indicates the year in which something (such as a concept, method, or product) was first introduced or presented in a publication.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff1a4448190b5559f440d264442 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.