Triple
T11823305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Locksley Hall |
E281191
|
entity |
| Predicate | authorLiteraryMovement |
P56599
|
FINISHED |
| Object | Victorian poetry |
—
|
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: Victorian poetry | Statement: [Locksley Hall, authorLiteraryMovement, Victorian poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorLiteraryMovement Context triple: [Locksley Hall, authorLiteraryMovement, Victorian poetry]
-
A.
literaryMovement
Indicates the artistic or intellectual movement in literature with which a work, author, or text is associated or to which it belongs.
-
B.
literaryAuthor
Indicates that one entity is the author or writer of a literary work represented by the other entity.
-
C.
literaryPeriodOfWork
chosen
Indicates the literary period or movement to which a particular work belongs.
-
D.
literaryMuseOf
Indicates a relationship in which one entity serves as the creative inspiration or muse for another entity’s literary work.
-
E.
literaryInfluence
Indicates that one entity has had a significant impact on the style, themes, or development of another entity’s literary work.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.