Triple
T15959988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man of Constant Sorrow |
E387031
|
entity |
| Predicate | hasVocalPerspective |
P120611
|
FINISHED |
| Object | first-person narrative |
—
|
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: first-person narrative | Statement: [Man of Constant Sorrow, hasVocalPerspective, first-person narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalPerspective Context triple: [Man of Constant Sorrow, hasVocalPerspective, first-person narrative]
-
A.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
B.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
C.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
-
E.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:53 a.m.