Triple
T5110385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Ferrars |
E115198
|
entity |
| Predicate | disinheritedReason |
P41735
|
FINISHED |
| Object | refusal to marry Miss Morton |
—
|
LITERAL FINISHED |
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: refusal to marry Miss Morton | Statement: [Edward Ferrars, disinheritedReason, refusal to marry Miss Morton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disinheritedReason Context triple: [Edward Ferrars, disinheritedReason, refusal to marry Miss Morton]
-
A.
reasonForLossOfSuccessionRights
chosen
Indicates the specific cause or circumstance that led to an individual losing their rights of succession.
-
B.
reasonForDismissal
Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
-
C.
abandonedReason
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
-
D.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
E.
reasonForDisqualification
Indicates the specific cause or justification for which an entity was deemed ineligible or disqualified from consideration or participation.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ad362c8190b9cbded390aaea3c |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.