Triple
T26105929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacraments of the Sick |
E658534
|
entity |
| Predicate | historicalNameAssociated |
P175129
|
FINISHED |
| Object | Extreme Unction |
—
|
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: Extreme Unction | Statement: [Sacraments of the Sick, historicalNameAssociated, Extreme Unction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameAssociated Context triple: [Sacraments of the Sick, historicalNameAssociated, Extreme Unction]
-
A.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
-
B.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
C.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
D.
isHistoricalName
chosen
Indicates that a given name is a former or past designation historically used for an entity.
-
E.
historicalEntityAssociated
Indicates that one entity has a documented historical connection, relevance, or involvement with 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 26, 2026, 7:58 p.m.