Triple
T19169219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Setsuko Matsudaira |
E469269
|
entity |
| Predicate | afterHusbandDeathRole |
P134697
|
FINISHED |
| Object | patron of cultural and charitable activities |
—
|
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: patron of cultural and charitable activities | Statement: [Setsuko Matsudaira, afterHusbandDeathRole, patron of cultural and charitable activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterHusbandDeathRole Context triple: [Setsuko Matsudaira, afterHusbandDeathRole, patron of cultural and charitable activities]
-
A.
afterMarriageRole
Indicates the role or status an entity assumes following a marriage event.
-
B.
styleAfterHusbandDeath
Indicates that an entity adopts or changes its style in response to, or following, the death of its husband.
-
C.
spouseStatusAfterDeath
Indicates the marital status or spousal relationship of a person after the death of their spouse.
-
D.
subsequentReactionToHusbandsDeath
Indicates a reaction or response that occurs after and as a result of the husband's death.
-
E.
spouseDeath
Indicates that one person's spouse has died, marking the event of the spouse's death in relation to that person.
- F. None of above. chosen
Provenance (4 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f162ac648190a5f60c6a77b68304 |
completed | April 20, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.