Triple
T34294962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arland Dean Williams Jr. |
E879998
|
entity |
| Predicate | identifiedPosthumously |
P4225
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Arland Dean Williams Jr., identifiedPosthumously, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiedPosthumously Context triple: [Arland Dean Williams Jr., identifiedPosthumously, true]
-
A.
isPosthumous
chosen
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
B.
isPosthumousNameOf
Indicates that one name is a posthumous title or designation that was given to and refers to a person after their death.
-
C.
posthumousAssociation
Indicates an association or connection between entities that is established, recognized, or relevant only after one of the entities has died.
-
D.
notedPosthumouslyBy
Indicates that information about an entity was recorded, mentioned, or recognized by someone only after that entity’s death.
-
E.
posthumousRealization
Indicates the recognition, understanding, or appreciation of something about an entity that occurs only after that entity has died.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f731cc6d1881908f80386ef4d70a09 |
completed | May 3, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69f7317779e08190bf85777578221a6b |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:57 a.m.