Triple
T3926140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A River Ain’t Too Much to Love |
E93280
|
entity |
| Predicate | nextWorkReleaseDate |
P17928
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [A River Ain’t Too Much to Love, nextWorkReleaseDate, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nextWorkReleaseDate Context triple: [A River Ain’t Too Much to Love, nextWorkReleaseDate, 2007]
-
A.
nextWorkReleaseYear
chosen
Indicates the year in which the next work in a sequence or series is scheduled to be released.
-
B.
nextSingleReleaseYear
Indicates the calendar year in which the entity’s next individual (non-album) release is scheduled or occurred.
-
C.
nextAlbumReleaseDate
Indicates the scheduled or actual calendar date on which the next album by an artist or group is released.
-
D.
nextEdition
Indicates that one entity is the immediate subsequent edition or version that follows another in a sequence.
-
E.
laterWork
Indicates that one work was created, published, or produced after another work in time.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeed80a1e48190aa39748b9db42701 |
completed | March 9, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.