Triple
T25212875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Performance |
E631736
|
entity |
| Predicate | releaseOrder |
P60900
|
FINISHED |
| Object | posthumous in Donny Hathaway’s catalog |
—
|
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: posthumous in Donny Hathaway’s catalog | Statement: [In Performance, releaseOrder, posthumous in Donny Hathaway’s catalog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseOrder Context triple: [In Performance, releaseOrder, posthumous in Donny Hathaway’s catalog]
-
A.
releaseSequence
chosen
Indicates the ordered succession in which related items, such as versions or installments, are released over time.
-
B.
releasedBefore
Indicates that one entity was released at an earlier time or date than another entity.
-
C.
releaseSchedule
Indicates the planned timing and sequence for when something (such as a product, update, or content) will be made available or launched.
-
D.
releasedDuring
Indicates that one entity was released within the time period defined by 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47b8a42a4819094f1f77087a8c271 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:58 p.m.