Triple
T37888268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Bruton |
E945056
|
entity |
| Predicate | doesNotInviteToLuncheon |
P4300
|
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: [Lady Bruton, doesNotInviteToLuncheon, Clarissa Dalloway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotInviteToLuncheon Context triple: [Lady Bruton, doesNotInviteToLuncheon, Clarissa Dalloway]
-
A.
doesNotParticipateIn
Indicates that an entity is explicitly not involved in, associated with, or taking part in a specified activity, event, or process.
-
B.
mayReceiveInvitationTo
Indicates that one entity is allowed or eligible to be sent an invitation by another entity.
-
C.
isInvited
Indicates that one entity has extended an invitation to another entity to participate in or attend something.
-
D.
doesNot
chosen
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
doesNotBan
Indicates that one entity allows or permits another entity or action by explicitly not prohibiting it.
- 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:19 p.m.