Triple
T22750779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rostova |
E562688
|
entity |
| Predicate | genreOfWorkWhereNotable |
P12590
|
FINISHED |
| Object | historical 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: historical novel | Statement: [Rostova, genreOfWorkWhereNotable, historical novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfWorkWhereNotable Context triple: [Rostova, genreOfWorkWhereNotable, historical novel]
-
A.
notableWorkGenre
chosen
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
B.
genreOfWorkHonored
Indicates the specific genre or type of creative work for which an honor, award, or recognition is given.
-
C.
genreOfWorkHeWrites
Indicates that a person is an author who writes works belonging to a particular genre.
-
D.
notableTypeOfWork
Indicates that a work is a significant or defining example within a particular type or category of work associated with an entity.
-
E.
authorNotableWork
Indicates that a person is the creator or writer of a specific notable work, such as a book, article, or other significant publication.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b8e9408190b251700d3386a1b9 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:24 p.m.