Triple
T21926449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephemerides |
E541454
|
entity |
| Predicate | approximateDateOfFirstEdition |
P141043
|
FINISHED |
| Object | 1470s |
—
|
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: 1470s | Statement: [Ephemerides, approximateDateOfFirstEdition, 1470s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateOfFirstEdition Context triple: [Ephemerides, approximateDateOfFirstEdition, 1470s]
-
A.
approximateDateOfFirstPrinting
chosen
Indicates the estimated or uncertain date when an item was first printed.
-
B.
firstEditionStartDate
Indicates the date on which the first edition of something (such as a work, product, or event series) was initially released or began.
-
C.
inceptionOfEdition
Indicates the event or point in time at which a particular edition of a work is first created, initiated, or brought into existence.
-
D.
firstTypicalEditionYear
Indicates the year in which the first typical or standard edition of a work was published or officially issued.
-
E.
firstBookPublicationDate
Indicates the calendar date on which an entity’s first book was officially published.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123fb6af08190b3562f547d4d2895 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:46 p.m.