Triple
T24090328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee of 1550 |
E596768
|
entity |
| Predicate | mainIndulgenceType |
P70962
|
FINISHED |
| Object | plenary indulgence |
—
|
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: plenary indulgence | Statement: [Jubilee of 1550, mainIndulgenceType, plenary indulgence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainIndulgenceType Context triple: [Jubilee of 1550, mainIndulgenceType, plenary indulgence]
-
A.
hasTypeOfIndulgence
chosen
Indicates that an entity is associated with a specific kind or category of indulgence it involves or permits.
-
B.
hasSpecialIndulgence
Indicates that one entity grants or possesses a particular privilege, exemption, or favor specifically afforded to another entity.
-
C.
typicalFlavor
Indicates that something characteristically has or is associated with a particular flavor.
-
D.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
E.
conditionForIndulgence
Indicates that one situation or state serves as the required basis or prerequisite for granting an indulgence or leniency in another.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc2d405881909469aa95901ab87b |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:51 p.m.