Triple
T16525759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Past Tense |
E401430
|
entity |
| Predicate | belongsToLiteraryCategory |
P22130
|
FINISHED |
| Object | popular 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: popular fiction | Statement: [Past Tense, belongsToLiteraryCategory, popular fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToLiteraryCategory Context triple: [Past Tense, belongsToLiteraryCategory, popular fiction]
-
A.
hasLiteraryConnection
Indicates a relationship in which one entity is connected to another through a literary link, such as authorship, reference, influence, adaptation, or shared appearance in written works.
-
B.
literaryGenreOfWork
chosen
Indicates that a work belongs to or is classified under a particular literary genre.
-
C.
literaryGenreOfSourceWork
Indicates that a work belongs to, or is characterized by, a particular literary genre.
-
D.
hasLiterarySignificance
Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
-
E.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed3f0388190a9f03473c37dfc46 |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.