Triple
T3926138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A River Ain’t Too Much to Love |
E93280
|
entity |
| Predicate | previousWorkReleaseDate |
P17927
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [A River Ain’t Too Much to Love, previousWorkReleaseDate, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousWorkReleaseDate Context triple: [A River Ain’t Too Much to Love, previousWorkReleaseDate, 2003]
-
A.
previousWorkReleaseYear
chosen
Indicates the year in which an earlier or prior work in a sequence or related set was released.
-
B.
nextWorkReleaseYear
Indicates the year in which the next work in a sequence or series is scheduled to be released.
-
C.
previousProduction
Indicates that one production event, item, or version occurred or was created before another in a sequence.
-
D.
lastWork
Indicates that one entity is the most recent work (e.g., creation, project, or publication) associated with another entity.
-
E.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
- 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_69aeed7f3cc881909464db1970ba39ae |
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.