Triple
T23440502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selected Poems, 1935–1985 |
E565384
|
entity |
| Predicate | hasTemporalCoverageEnd |
P129764
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [Selected Poems, 1935–1985, hasTemporalCoverageEnd, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalCoverageEnd Context triple: [Selected Poems, 1935–1985, hasTemporalCoverageEnd, 1985]
-
A.
hasTemporalEnd
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
B.
chronologicalCoverageEnd
chosen
Indicates the point in time at which the temporal or chronological span of something (such as a resource, event, or record) comes to an end.
-
C.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
D.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
E.
temporalAuthorityEndedBy
Indicates that a period of temporal authority or secular power held by one entity comes to an end as a result of an action or event caused by another entity.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5df28288190936f16b017a20bc0 |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:50 p.m.