Triple
T22073375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RV 269 (Spring) |
E545463
|
entity |
| Predicate | hasAssociatedSonnet |
P52908
|
FINISHED |
| Object | Sonnet describing springtime scenes |
—
|
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: Sonnet describing springtime scenes | Statement: [RV 269 (Spring), hasAssociatedSonnet, Sonnet describing springtime scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedSonnet Context triple: [RV 269 (Spring), hasAssociatedSonnet, Sonnet describing springtime scenes]
-
A.
hasCanonicalPoem
Indicates that an entity is associated with a poem recognized as its standard or authoritative version.
-
B.
hasPoemSetIn
Indicates that a poem is set in or takes place within a particular location or setting.
-
C.
numberOfSonnets
Indicates the quantity of sonnets associated with a given entity.
-
D.
notableSonnetGroup
Indicates that one entity is a notable or significant group or collection of sonnets associated with the other entity.
-
E.
associatedWithPoem
chosen
Indicates a relationship in which an entity is connected or linked to a particular poem, such as by authorship, subject, reference, or contextual association.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12889f504819089830202e64d97b0 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.