Triple
T954316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subterranean Homesick Blues |
E20591
|
entity |
| Predicate | isTitleAlludingTo |
P4929
|
FINISHED |
| Object | subterranean homesickness |
—
|
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: subterranean homesickness | Statement: [Subterranean Homesick Blues, isTitleAlludingTo, subterranean homesickness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTitleAlludingTo Context triple: [Subterranean Homesick Blues, isTitleAlludingTo, subterranean homesickness]
-
A.
titleAlludesTo
chosen
Indicates that one title makes an indirect or suggestive reference to the content, theme, or another work associated with the other.
-
B.
isTitleFor
Indicates that one entity serves as the official title or name designation for another entity.
-
C.
isTitleCharacterOfSong
Indicates that a character is mentioned in or constitutes the title of a specific song.
-
D.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
E.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3da8d508190b56b29d7f235d2c4 |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.