Triple
T24796303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidney family |
E620392
|
entity |
| Predicate | literaryContribution |
P15594
|
FINISHED |
| Object | Elizabethan 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: Elizabethan poetry | Statement: [Sidney family, literaryContribution, Elizabethan poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryContribution Context triple: [Sidney family, literaryContribution, Elizabethan poetry]
-
A.
literaryInfluence
Indicates that one entity has had a significant impact on the style, themes, or development of another entity’s literary work.
-
B.
hasLiterarySignificance
chosen
Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
-
C.
literaryAuthor
Indicates that one entity is the author or writer of a literary work represented by the other entity.
-
D.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
E.
literaryCenter
Indicates that a location functions as a primary hub or focal point for literary activity, such as writing, publishing, or literary culture.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:48 a.m.