Triple
T5841161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ode: Intimations of Immortality |
E129596
|
entity |
| Predicate | compositionPeriodStart |
P10338
|
FINISHED |
| Object | 1802 |
—
|
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: 1802 | Statement: [Ode: Intimations of Immortality, compositionPeriodStart, 1802]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionPeriodStart Context triple: [Ode: Intimations of Immortality, compositionPeriodStart, 1802]
-
A.
beganInYear
chosen
Indicates that an event, process, or state started in a specific calendar year.
-
B.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
-
C.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
-
D.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
E.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.