Triple
T2431383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNCC Freedom Singers |
E52852
|
entity |
| Predicate | notableSongType |
P30697
|
FINISHED |
| Object | call-and-response songs |
—
|
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: call-and-response songs | Statement: [SNCC Freedom Singers, notableSongType, call-and-response songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSongType Context triple: [SNCC Freedom Singers, notableSongType, call-and-response songs]
-
A.
notableSongWrittenFor
Indicates that a particular song was specifically written for a given person, group, work, event, or purpose.
-
B.
notableSongCharacteristic
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
C.
notableComposition
Indicates that an entity is a significant or well-known work created by another entity, such as a notable musical, literary, or artistic composition.
-
D.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
E.
songType
chosen
Indicates the specific category or genre that a given song belongs to.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:43 p.m.