Triple
T28651113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The End of the Journey |
E725198
|
entity |
| Predicate | isSectionOfGenre |
P116833
|
FINISHED |
| Object | late-19th-century fantasy romance |
—
|
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: late-19th-century fantasy romance | Statement: [The End of the Journey, isSectionOfGenre, late-19th-century fantasy romance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSectionOfGenre Context triple: [The End of the Journey, isSectionOfGenre, late-19th-century fantasy romance]
-
A.
hasGenreInSeries
Indicates that a particular genre is associated with, or applies to, a work as it appears within a specific series.
-
B.
includedInGenreCollection
Indicates that something is a member of, or contained within, a specific genre-based collection.
-
C.
isAssociatedWithSubgenre
Indicates that one entity has a connection or linkage to a specific subgenre of a broader category.
-
D.
hasGenreInFiction
chosen
Indicates that a work of fiction belongs to or is categorized under a specific literary genre.
-
E.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:52 a.m.