Triple
T29827506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Day-O |
E757421
|
entity |
| Predicate | isRefrainOf |
P142054
|
FINISHED |
| Object | traditional Jamaican mento song |
—
|
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: traditional Jamaican mento song | Statement: [Day-O, isRefrainOf, traditional Jamaican mento song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRefrainOf Context triple: [Day-O, isRefrainOf, traditional Jamaican mento song]
-
A.
hasRefrainRelatedTo
Indicates that a refrain (repeated musical or textual section) in one work is thematically or content-wise related to another specified subject or element.
-
B.
containsRefrainAlsoFoundIn
chosen
Indicates that one entity includes a refrain that is also present in another entity.
-
C.
refrain
Indicates that an entity deliberately holds back from performing a particular action or behavior.
-
D.
refrainType
Indicates the specific kind or category of refrain (repeated passage) associated with a musical or poetic work or section.
-
E.
refrainTranslation
Indicates that one expression is a translation of the repeated or recurring part (refrain) of another expression, typically in a different language.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f675999c988190a5e220a4a2d45e50 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 5:32 p.m.