Triple
T25508115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acrasia |
E639298
|
entity |
| Predicate | workPublicationStartDate |
P138701
|
FINISHED |
| Object | 1590 |
—
|
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: 1590 | Statement: [Acrasia, workPublicationStartDate, 1590]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPublicationStartDate Context triple: [Acrasia, workPublicationStartDate, 1590]
-
A.
yearOfWorkPublicationStart
chosen
Indicates the calendar year in which a given work was first published or made publicly available.
-
B.
folioPublicationYear
Indicates the year in which a particular folio was published.
-
C.
relatedWorkPublicationYear
Indicates the year in which a related work associated with the primary entity was published.
-
D.
workPublishedBy
Indicates that a work (such as a book, article, or other creation) has been issued or made publicly available by a particular publisher or publishing entity.
-
E.
notableWorkPeriodStart
Indicates the point in time when an entity’s period of producing its notable work or works begins.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 2:47 p.m.