Triple
T37888186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Walsh |
E945054
|
entity |
| Predicate | wasSuitorOf |
P26260
|
FINISHED |
| Object | Clarissa Dalloway |
—
|
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: Clarissa Dalloway | Statement: [Peter Walsh, wasSuitorOf, Clarissa Dalloway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSuitorOf Context triple: [Peter Walsh, wasSuitorOf, Clarissa Dalloway]
-
A.
rivalForMarriageOf
Indicates that one entity is a romantic competitor with another entity for the opportunity to marry a specific third entity.
-
B.
hasSuitors
chosen
Indicates that an entity is the object of romantic or marital interest from one or more other entities.
-
C.
proposedBride
Indicates that one entity has been put forward or suggested as a potential bride for another entity.
-
D.
isFianceeOf
Indicates that one person is the engaged-to-be-married partner of another person.
-
E.
choseAsHusband
Indicates that one entity selected another entity to be her husband, typically as a marital partner.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.