Triple
T6867357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary McAfee Atkins |
E158440
|
entity |
| Predicate | hasBequest |
P73110
|
FINISHED |
| Object | endowment for an art museum in Kansas City |
—
|
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: endowment for an art museum in Kansas City | Statement: [Mary McAfee Atkins, hasBequest, endowment for an art museum in Kansas City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBequest Context triple: [Mary McAfee Atkins, hasBequest, endowment for an art museum in Kansas City]
-
A.
bequeathedBy
Indicates that something has been left or passed on to an entity through the will or inheritance of another entity.
-
B.
notableBequest
chosen
Indicates that one entity is a significant or historically notable bequest, legacy, or inheritance made by another entity.
-
C.
bequestLocation
Indicates the place or institution where a bequest is directed, stored, or intended to be received.
-
D.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
E.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:21 p.m.