Triple
T24046737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Salting |
E595543
|
entity |
| Predicate | bequestRecipient |
P52361
|
FINISHED |
| Object | British Museum |
—
|
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: British Museum | Statement: [George Salting, bequestRecipient, British Museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bequestRecipient Context triple: [George Salting, bequestRecipient, British Museum]
-
A.
bequestLocation
Indicates the place or institution where a bequest is directed, stored, or intended to be received.
-
B.
bequeathedBy
Indicates that something has been left or passed on to an entity through the will or inheritance of another entity.
-
C.
bequestEstablished
Indicates that a bequest has been formally created or put into effect, establishing a legally recognized transfer of assets upon someone’s death.
-
D.
recipientOf
chosen
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
E.
grantRecipient
Indicates that one entity is the recipient or beneficiary of a grant provided by 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9ca5a18819086da68b69eed8cc1 |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:17 p.m.