Triple
T15520030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmund Ignatius Rice |
E368938
|
entity |
| Predicate | hasPosthumousStatus |
P4225
|
FINISHED |
| Object | Venerable in the Catholic Church |
—
|
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: Venerable in the Catholic Church | Statement: [Edmund Ignatius Rice, hasPosthumousStatus, Venerable in the Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPosthumousStatus Context triple: [Edmund Ignatius Rice, hasPosthumousStatus, Venerable in the Catholic Church]
-
A.
hasPosthumousRelease
Indicates that a work was released or made publicly available only after its creator’s death.
-
B.
isPosthumous
chosen
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
C.
isPosthumousAwardRecipientOf
Indicates that an entity received an award that was granted after their death.
-
D.
isPosthumousTributeTo
Indicates that something (such as a work, event, or honor) is created or given as a tribute to a person after that person has died.
-
E.
canBeAwardedPosthumously
Indicates that something (such as an honor, title, or award) is eligible to be granted to a person after their death.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e040343d9c8190a7d1f197c108bd9d |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:04 a.m.