Triple
T31965111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Knight of Ghosts and Shadows |
E816152
|
entity |
| Predicate | blendsSubgenres |
P85590
|
FINISHED |
| Object | space opera adventure |
—
|
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: space opera adventure | Statement: [A Knight of Ghosts and Shadows, blendsSubgenres, space opera adventure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blendsSubgenres Context triple: [A Knight of Ghosts and Shadows, blendsSubgenres, space opera adventure]
-
A.
combinesGenre
chosen
Indicates that an entity integrates or merges multiple genres into a single combined form or work.
-
B.
subgenre
Indicates that one genre is a more specific, subordinate category within a broader parent genre.
-
C.
isOnGenreBlendingAlbum
Indicates that something (typically a song or track) appears on an album characterized by blending or combining multiple musical genres.
-
D.
isAssociatedWithSubgenre
Indicates that one entity has a connection or linkage to a specific subgenre of a broader category.
-
E.
secondaryGenre
Indicates that an entity (such as a work or item) has an additional, non-primary genre classification associated with it.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2e9f9f48190b52e9381133c102d |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:09 a.m.