Triple
T22863365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladies and Gentlemen... the Grateful Dead |
E566984
|
entity |
| Predicate | recordedEndDate |
P33169
|
FINISHED |
| Object | 1971-04-29 |
—
|
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: 1971-04-29 | Statement: [Ladies and Gentlemen... the Grateful Dead, recordedEndDate, 1971-04-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedEndDate Context triple: [Ladies and Gentlemen... the Grateful Dead, recordedEndDate, 1971-04-29]
-
A.
recordedOnDate
Indicates the specific calendar date on which an event, action, or piece of information was formally recorded.
-
B.
recordingEnd
chosen
Indicates the point in time or event at which a recording process or recorded segment concludes.
-
C.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
D.
announcedEnd
Indicates that an entity has publicly declared or made known the termination or conclusion of something.
-
E.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eff1c18819081dc9dfc1816f746 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.