Triple
T21268992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devotions |
E524204
|
entity |
| Predicate | spansPeriodOfAuthorCareer |
P47065
|
FINISHED |
| Object | several decades |
—
|
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: several decades | Statement: [Devotions, spansPeriodOfAuthorCareer, several decades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spansPeriodOfAuthorCareer Context triple: [Devotions, spansPeriodOfAuthorCareer, several decades]
-
A.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
B.
authorLifespanContext
Indicates the temporal or historical context of an author’s life span in relation to other events, periods, or entities.
-
C.
refersToEraOfCareer
Indicates that one entity specifies or denotes the particular era or phase within another entity’s career.
-
D.
activeYearsInLiterature
chosen
Indicates the span of years during which an entity was actively producing or contributing to literary works.
-
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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73651115081908b5083ba818a6bb1 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4:01 p.m.