Triple
T2250981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clara Reeve |
E49614
|
entity |
| Predicate | hasWorkInGenre |
P14417
|
FINISHED |
| Object | historical 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: historical fiction | Statement: [Clara Reeve, hasWorkInGenre, historical fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkInGenre Context triple: [Clara Reeve, hasWorkInGenre, historical fiction]
-
A.
workedOnGenre
chosen
Indicates that an entity (such as a person or organization) has done work related to a particular genre.
-
B.
basedOnWorkGenre
Indicates that one entity’s genre classification is derived from or determined by the genre of another work.
-
C.
hasNotableGenre
Indicates that an entity is significantly associated with a particular genre, such that the genre is especially characteristic or noteworthy for that entity.
-
D.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
E.
hasGenreInfluenceOn
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11d04688190abc04fac3a1804a9 |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.