Triple
T26163993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rag Mop |
E654194
|
entity |
| Predicate | hasSpellingGimmick |
P53251
|
FINISHED |
| Object | title spelled out in lyrics |
—
|
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: title spelled out in lyrics | Statement: [Rag Mop, hasSpellingGimmick, title spelled out in lyrics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpellingGimmick Context triple: [Rag Mop, hasSpellingGimmick, title spelled out in lyrics]
-
A.
spellingGimmick
chosen
Indicates a distinctive or unconventional way of spelling something used for effect or branding rather than standard orthography.
-
B.
includesSpellType
Indicates that one entity (such as a spell list, spellbook, or ability) contains or covers a particular type or category of spell.
-
C.
hasSpellingWithAccent
Indicates that one form of a word or name is spelled using accented characters compared to another form.
-
D.
underSpellBy
Indicates that one entity is magically influenced, controlled, or enchanted by another entity.
-
E.
effectOnSpelling
Indicates a relationship where one factor influences or alters the way something is spelled.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 26, 2026, 8:31 p.m.