Triple
T12903239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How do I love thee? (Sonnet 43) |
E308662
|
entity |
| Predicate | hasSestet |
P107361
|
FINISHED |
| Object | final six lines |
—
|
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: final six lines | Statement: [How do I love thee? (Sonnet 43), hasSestet, final six lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSestet Context triple: [How do I love thee? (Sonnet 43), hasSestet, final six lines]
-
A.
hasSetPiece
Indicates that an event, scene, or work includes a distinct, often elaborate set piece as a notable component.
-
B.
hasMysterySet
Indicates that an entity possesses or includes a collection or configuration whose nature or details are unknown or intentionally concealed.
-
C.
hasBasicCardSet
Indicates that an entity is associated with or includes a fundamental or default set of cards.
-
D.
hasSept
Indicates that one entity possesses, contains, or is associated with a sept (a subdivision or clan group) in relation to another entity.
-
E.
hasSpade
Indicates that one entity possesses, holds, or is equipped with a spade in relation to another context or entity.
- F. None of above. chosen
Provenance (4 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971820e008190bf8bc7c392c8bcbb |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:40 p.m.