Triple
T35013822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosmeris |
E1009999
|
entity |
| Predicate | genreUniverse |
P31344
|
FINISHED |
| Object | high 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: high fantasy | Statement: [Bosmeris, genreUniverse, high fantasy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreUniverse Context triple: [Bosmeris, genreUniverse, high fantasy]
-
A.
inUniverseGenre
Indicates that a work’s genre classification exists within the fictional universe itself (e.g., as an in-story show, book, or media type), rather than being an external, real-world genre label.
-
B.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
C.
genre
Indicates the artistic or thematic category to which a work (such as a book, film, or song) belongs.
-
D.
fandomGenre
Indicates that something belongs to, is associated with, or is categorized under a particular fandom-related genre.
-
E.
hasFictionalUniverseGenre
chosen
Indicates that a fictional universe is associated with a particular genre that characterizes its overall style, themes, or narrative type.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.