Triple
T35095135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowick |
E1012845
|
entity |
| Predicate | literaryPeriodOfWorkItAppearsIn |
P56599
|
FINISHED |
| Object | Victorian literature |
—
|
NE NERFINISHED |
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: Victorian literature | Statement: [Lowick, literaryPeriodOfWorkItAppearsIn, Victorian literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryPeriodOfWorkItAppearsIn Context triple: [Lowick, literaryPeriodOfWorkItAppearsIn, Victorian literature]
-
A.
literaryPeriodOfWork
chosen
Indicates the literary period or movement to which a particular work belongs.
-
B.
literaryPeriodOfSubject
Indicates the literary period or movement with which the subject is associated.
-
C.
literaryWorkSetInRegion
Indicates that a literary work’s narrative or events primarily take place within a specified geographic region.
-
D.
literaryGenreOfWorkAppearedIn
Indicates the literary genre of the work in which a given entity (such as a text, character, or element) appears.
-
E.
attestedInWorksOf
Indicates that something (such as a claim, form, or usage) is documented or evidenced within the works produced by a particular author or creator.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:01 p.m.