Triple
T33849818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Someday When Things Are Good |
E867589
|
entity |
| Predicate | notableCoWriter |
P89591
|
FINISHED |
| Object | Leona Williams |
E247447
|
NE 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: Leona Williams | Statement: [Someday When Things Are Good, notableCoWriter, Leona Williams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCoWriter Context triple: [Someday When Things Are Good, notableCoWriter, Leona Williams]
-
A.
notableLyricist
Indicates that the subject is a lyricist who is particularly distinguished or well-known for their work.
-
B.
notableSongwriterOn
chosen
Indicates that one entity is recognized as a notable songwriter contributing to or associated with another entity (such as a musical work or recording).
-
C.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
-
D.
notableAuthorMember
Indicates that an entity is a notable or distinguished author who is a member of a particular group, organization, or collection.
-
E.
notableCollaboration
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
- F. None of above.
Provenance (4 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ae07ed2081908432b6c81459803c |
completed | June 22, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:47 a.m.