Triple
T12004100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emotional Rescue |
E285736
|
entity |
| Predicate | recordingEndYear |
P214
|
FINISHED |
| Object | 1980 |
—
|
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: 1980 | Statement: [Emotional Rescue, recordingEndYear, 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingEndYear Context triple: [Emotional Rescue, recordingEndYear, 1980]
-
A.
recordingYear
Indicates the specific calendar year in which something (such as audio, video, or data) was recorded.
-
B.
serializationEndYear
Indicates the year in which the serialization or serialized publication of an entity concluded.
-
C.
recordStartYear
Indicates the calendar year in which a particular record, entry, or data instance first began or was created.
-
D.
endYear
chosen
Indicates the year in which an event, state, or relationship comes to an end.
-
E.
endYearApprox
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c481a48190b311d6809808ef1b |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.