Triple
T7136331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulliver's Travels |
E166314
|
entity |
| Predicate | literaryGenreFeature |
P22130
|
FINISHED |
| Object | travel narrative parody |
—
|
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: travel narrative parody | Statement: [Gulliver's Travels, literaryGenreFeature, travel narrative parody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryGenreFeature Context triple: [Gulliver's Travels, literaryGenreFeature, travel narrative parody]
-
A.
literaryGenreOfWork
chosen
Indicates that a work belongs to or is classified under a particular literary genre.
-
B.
literaryFeature
Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
-
C.
fictionalGenre
Indicates that a work of fiction belongs to or is categorized under a particular narrative genre or style.
-
D.
literaryGenreFamily
Indicates that one literary genre belongs to, is a subtype of, or is otherwise grouped within a broader family of related literary genres.
-
E.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e6926d748190bc8c150fc1860531 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.