Triple
T12201905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ghost |
E290734
|
entity |
| Predicate | hasAliasTheme |
P52367
|
FINISHED |
| Object | ghost-related persona in lyrics and branding |
—
|
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: ghost-related persona in lyrics and branding | Statement: [The Ghost, hasAliasTheme, ghost-related persona in lyrics and branding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAliasTheme Context triple: [The Ghost, hasAliasTheme, ghost-related persona in lyrics and branding]
-
A.
usesAliasTheme
Indicates that one entity adopts or operates under an alternative thematic identity or label associated with another entity.
-
B.
hasThemeType
Indicates that something is associated with or characterized by a particular thematic category or type.
-
C.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
-
D.
hasThemeConnection
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
-
E.
hasNicknameTheme
chosen
Indicates that an entity’s nickname is based on or associated with a particular theme or motif.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.