Triple
T37888185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Walsh |
E945054
|
entity |
| Predicate | hasEnduringAttachmentTo |
P196532
|
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, hasEnduringAttachmentTo, Clarissa Dalloway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnduringAttachmentTo Context triple: [Peter Walsh, hasEnduringAttachmentTo, Clarissa Dalloway]
-
A.
hasAttachmentOrgan
Indicates that one entity possesses a specific anatomical or structural organ used to attach, anchor, or fasten it to another entity or substrate.
-
B.
hasDetachment
Indicates that an entity is separated, disconnected, or removed from another entity or its original position.
-
C.
supportsAttachments
Indicates that the subject is capable of handling or allowing the inclusion of file or data attachments in its operation or context.
-
D.
permanentlyAttachedSince
Indicates that one entity has been fixed or joined to another in a way intended to be lasting, starting from a specific point in time.
-
E.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: May 3, 2026, 4:19 p.m.