Triple
T38029087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. R. Johnson |
E948857
|
entity |
| Predicate | wroteMusicForLyricsBy |
P189970
|
FINISHED |
| Object | James Weldon Johnson |
E57333
|
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: James Weldon Johnson | Statement: [J. R. Johnson, wroteMusicForLyricsBy, James Weldon Johnson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteMusicForLyricsBy Context triple: [J. R. Johnson, wroteMusicForLyricsBy, James Weldon Johnson]
-
A.
lyricsWrittenWith
Indicates that the lyrics were written in collaboration with or using the assistance of another party or tool.
-
B.
hasWrittenLyricsFor
Indicates that one entity is the lyricist who has created the words for a song or musical work performed or associated with another entity.
-
C.
writesLyrics
Indicates that one entity creates or composes song lyrics for another entity (such as a song, musical work, or artist).
-
D.
hasLyricalWritingFor
Indicates that one entity provides or is characterized by lyrical or poetic writing created for another entity.
-
E.
wroteSongWith
Indicates that two or more entities collaborated in the creation or composition of a song.
- F. None of above. chosen
Provenance (5 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41c26948a08190a79fd76cb137d760 |
completed | June 29, 2026, 12:55 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:20 p.m.