Triple
T5026848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handbook of Spiritual Counsel |
E113195
|
entity |
| Predicate | timePeriodOfAuthor |
P44714
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Handbook of Spiritual Counsel, timePeriodOfAuthor, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfAuthor Context triple: [Handbook of Spiritual Counsel, timePeriodOfAuthor, 18th century]
-
A.
authorLifespanContext
chosen
Indicates the temporal or historical context of an author’s life span in relation to other events, periods, or entities.
-
B.
activeYearsInLiterature
Indicates the span of years during which an entity was actively producing or contributing to literary works.
-
C.
yearWorkWritten
Indicates the year in which a particular work was written or created.
-
D.
publicationPeriod
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
E.
workInChronologyOfAuthor
Indicates that a work appears within, and is ordered as part of, the chronological sequence of an author's creations or publications.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738c3aac81908fb6a5c70c97a394 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.