Triple
T5111866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Henry Dashwood |
E115230
|
entity |
| Predicate | inheritsEstateFrom |
P45732
|
FINISHED |
| Object | his uncle at Norland Park |
—
|
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: his uncle at Norland Park | Statement: [Mr. Henry Dashwood, inheritsEstateFrom, his uncle at Norland Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritsEstateFrom Context triple: [Mr. Henry Dashwood, inheritsEstateFrom, his uncle at Norland Park]
-
A.
inheritsWealth
Indicates that one entity receives wealth or assets passed down from another, typically after the latter’s death.
-
B.
bequeathedBy
chosen
Indicates that something has been left or passed on to an entity through the will or inheritance of another entity.
-
C.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
D.
inheritanceStatus
Indicates the type or condition of inheritance rights or succession status that applies between related parties.
-
E.
adoptedAsHeir
Indicates that one entity has been formally chosen and accepted as the legal heir or successor of another entity.
- 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_69bd75ca57e881908242def2a032902e |
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.