Triple
T12843384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonnets from the Portuguese |
E307110
|
entity |
| Predicate | rhymeSchemeType |
P8081
|
FINISHED |
| Object | Petrarchan sonnet |
—
|
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: Petrarchan sonnet | Statement: [Sonnets from the Portuguese, rhymeSchemeType, Petrarchan sonnet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rhymeSchemeType Context triple: [Sonnets from the Portuguese, rhymeSchemeType, Petrarchan sonnet]
-
A.
rhymeScheme
chosen
Indicates the pattern of end sounds in a sequence of lines, showing which lines rhyme with each other.
-
B.
hasRhymeSchemeFeature
Indicates that a poetic work exhibits a specific characteristic or pattern related to its rhyme scheme.
-
C.
hasRhymeStyle
Indicates that two linguistic elements share the same pattern or style of rhyming.
-
D.
poeticStructure
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used by another entity.
-
E.
hasRhymeLine
Indicates that one line of text rhymes with another line.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:35 p.m.