Triple
T3212514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norton Critical Editions |
E67311
|
entity |
| Predicate | coversGenre |
P33225
|
FINISHED |
| Object | novels |
—
|
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: novels | Statement: [Norton Critical Editions, coversGenre, novels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversGenre Context triple: [Norton Critical Editions, coversGenre, novels]
-
A.
coveredInGenre
chosen
Indicates that a work or item is associated with, categorized under, or treated within a particular genre.
-
B.
supportedGenre
Indicates that an entity (such as a system, service, or tool) is capable of handling, providing, or working with a specified genre.
-
C.
hasGenreScope
Indicates that something (such as a work, collection, or classification) is limited to, defined by, or applicable within a particular genre or set of genres.
-
D.
hasGenreInSeries
Indicates that a particular genre is associated with, or applies to, a work as it appears within a specific series.
-
E.
genreFeatures
Indicates that a particular genre is characterized or defined by certain features or attributes.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaabba8e481909118d9f888ddcd63 |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.