Triple
T36376814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saga, Volume 6 |
E895923
|
entity |
| Predicate | belongsToGenreBlend |
P181752
|
FINISHED |
| Object | science fiction/fantasy |
—
|
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: science fiction/fantasy | Statement: [Saga, Volume 6, belongsToGenreBlend, science fiction/fantasy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToGenreBlend Context triple: [Saga, Volume 6, belongsToGenreBlend, science fiction/fantasy]
-
A.
hasGenreBlend
chosen
Indicates that something combines or mixes multiple genres into a blended or hybrid form.
-
B.
hasGenreRelation
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
-
C.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
-
D.
hasTargetGenreCategory
Indicates that something is associated with or classified under a specific target genre category.
-
E.
associatedWithGenreElement
Indicates that something has a connection or linkage to a specific genre-related element (such as a motif, convention, or stylistic feature).
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: May 3, 2026, 4:10 p.m.