Triple
T109937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ichabod Crane |
E2224
|
entity |
| Predicate | literaryGenre |
P14
|
FINISHED |
| Object | Gothic fiction |
—
|
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: Gothic fiction | Statement: [Ichabod Crane, literaryGenre, Gothic fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryGenre Context triple: [Ichabod Crane, literaryGenre, Gothic fiction]
-
A.
genre
chosen
Indicates the artistic or thematic category to which a work (such as a book, film, or song) belongs.
-
B.
literaryTradition
Indicates a relationship where a work, practice, or expression belongs to, arises from, or participates in a particular established body of literary customs, styles, or conventions.
-
C.
literaryMovement
Indicates the artistic or intellectual movement in literature with which a work, author, or text is associated or to which it belongs.
-
D.
genreDiversity
Indicates the extent to which an entity involves, includes, or spans multiple distinct genres rather than being confined to a single genre.
-
E.
dramaticForm
Indicates that one entity is expressed, structured, or realized in the form of a particular dramatic genre or theatrical mode.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258b58efc8190959c86f73d67b744 |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25641058c8190b5b64509b35d8176 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.