Triple
T33700932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Wingfield |
E863453
|
entity |
| Predicate | feelsResponsibilityFor |
P81322
|
FINISHED |
| Object | Amanda Wingfield |
—
|
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: Amanda Wingfield | Statement: [Tom Wingfield, feelsResponsibilityFor, Amanda Wingfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feelsResponsibilityFor Context triple: [Tom Wingfield, feelsResponsibilityFor, Amanda Wingfield]
-
A.
responsibleFor
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
hasSocialObligationsTo
chosen
Indicates that one entity bears social duties, expectations, or responsibilities toward another entity.
-
C.
accountabilityTo
Indicates that one entity is responsible for explaining, justifying, or answering for its actions, decisions, or outcomes to another entity.
-
D.
accountableThrough
Indicates that one entity bears responsibility or can be held answerable by means of, or via the mechanism provided by, another entity or process.
-
E.
establishesLiabilityFor
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa8ca3808190be2fd9e5fb4c2146 |
completed | May 3, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.