Triple
T21443509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taji |
E529003
|
entity |
| Predicate | appearsInLiteraryForm |
P6480
|
FINISHED |
| Object | novel |
—
|
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: novel | Statement: [Taji, appearsInLiteraryForm, novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInLiteraryForm Context triple: [Taji, appearsInLiteraryForm, novel]
-
A.
hasLiteraryForm
chosen
Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
-
B.
hasPlaceInFiction
Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
-
C.
literaryWorkInStory
Indicates that one literary work is referenced, featured, or embedded within the narrative of another story.
-
D.
depictsLiteraryWork
Indicates that one entity visually represents, illustrates, or portrays the content, scenes, or themes of a specific literary work.
-
E.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b7055d148190ae3b52e10abd8fd2 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:05 p.m.