Triple
T25508850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonnet 31 "With how sad steps, O Moon" |
E639316
|
entity |
| Predicate | belovedCharacter |
P158613
|
FINISHED |
| Object | Stella |
—
|
NE NERFINISHED |
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: Stella | Statement: [Sonnet 31 "With how sad steps, O Moon", belovedCharacter, Stella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belovedCharacter Context triple: [Sonnet 31 "With how sad steps, O Moon", belovedCharacter, Stella]
-
A.
hasFictionalBeloved
Indicates that an entity has a romantic partner or beloved who exists only as a fictional character.
-
B.
mainCharactersAre
Indicates that the specified entities serve as the primary or central characters in a narrative or work.
-
C.
plotCharacter
Indicates a relationship where a character plays a role or participates in the narrative plot of a story or work.
-
D.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
-
E.
cultCharacter
Indicates that one entity is a character who is venerated, worshipped, or centrally revered within the cult associated with the other 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f80844488190bbbaa6bd2e487940 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:48 p.m.