Triple
T27880681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annals of My Early Life, 1806–1846 |
E705078
|
entity |
| Predicate | describesPeriodEnd |
P127067
|
FINISHED |
| Object | 1846 |
—
|
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: 1846 | Statement: [Annals of My Early Life, 1806–1846, describesPeriodEnd, 1846]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesPeriodEnd Context triple: [Annals of My Early Life, 1806–1846, describesPeriodEnd, 1846]
-
A.
documentedPeriodEnd
Indicates the point in time at which the documented period or interval associated with something comes to an end.
-
B.
associatedPeriodEnd
Indicates the ending point or final date of the time period with which something is associated.
-
C.
governedPeriodEnd
Indicates the point in time at which a governing authority’s control or jurisdiction over something comes to an end.
-
D.
narrativePeriodEnd
chosen
Indicates the point in time at which a described narrative, story, or event sequence comes to an end.
-
E.
recordedInPeriodEnd
Indicates that an event, transaction, or record is logged as occurring within the closing portion of a specified time period.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 6:29 p.m.