Triple
T1913102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kassaman |
E38153
|
entity |
| Predicate | lyricsWrittenWith |
P33895
|
FINISHED |
| Object | blood |
—
|
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: blood | Statement: [Kassaman, lyricsWrittenWith, blood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricsWrittenWith Context triple: [Kassaman, lyricsWrittenWith, blood]
-
A.
songWrittenBy
Indicates that a particular song was created or composed by a specific person or group.
-
B.
lyricist
Indicates that one entity is the writer of the words (lyrics) for a musical work associated with another entity.
-
C.
lyricsBy
Indicates that the lyrics of a song or musical work were written or authored by a specified person or entity.
-
D.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
E.
scriptUsedInLyrics
Indicates that a particular writing system or script is used to write or represent the lyrics of a song or musical work.
- F. None of above. chosen
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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb34c4a64819096e12b152b84c334 |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:35 p.m.