Triple
T21102936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malin |
E519955
|
entity |
| Predicate | nationalLiteraryContextOfWork |
P55714
|
FINISHED |
| Object | English literature |
—
|
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: English literature | Statement: [Malin, nationalLiteraryContextOfWork, English literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalLiteraryContextOfWork Context triple: [Malin, nationalLiteraryContextOfWork, English literature]
-
A.
hasLiteraryContext
chosen
Indicates that something is associated with, situated within, or explained by a particular literary context (such as a work, genre, period, or interpretive framework).
-
B.
literaryCenter
Indicates that a location functions as a primary hub or focal point for literary activity, such as writing, publishing, or literary culture.
-
C.
literaryUnit
Indicates that one entity is a distinct segment or component (such as a chapter, scene, or passage) within a larger literary work or text.
-
D.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
E.
literaryPeriodOfWork
Indicates the literary period or movement to which a particular work belongs.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b5ee8948190ac6e9e144d312c90 |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.