Triple
T19980629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonnet 29 |
E493806
|
entity |
| Predicate | voltaMarker |
P2130
|
FINISHED |
| Object | Yet in these thoughts myself almost despising |
—
|
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: Yet in these thoughts myself almost despising | Statement: [Sonnet 29, voltaMarker, Yet in these thoughts myself almost despising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voltaMarker Context triple: [Sonnet 29, voltaMarker, Yet in these thoughts myself almost despising]
-
A.
voltaPosition
Indicates the specific location or placement of a volta (a repeated section’s alternate ending) within a musical structure or score.
-
B.
markingFeature
Indicates a feature that serves as a distinguishing mark or identifier associated with an entity.
-
C.
marque
Indicates that one entity is the brand or make associated with another entity, such as a product, vehicle, or manufactured item.
-
D.
hasMarker
chosen
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
E.
trailsMarkedBy
Indicates that a trail or path is designated or identified by specific markers, signs, or blazes placed along its route.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d12d968819081e315ec4585cd9f |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:28 p.m.