Triple
T6466684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee of 1600 |
E142248
|
entity |
| Predicate | hasTypeOfIndulgence |
P70962
|
FINISHED |
| Object | plenary indulgence for pilgrims |
—
|
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 for pilgrims | Statement: [Jubilee of 1600, hasTypeOfIndulgence, plenary indulgence for pilgrims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfIndulgence Context triple: [Jubilee of 1600, hasTypeOfIndulgence, plenary indulgence for pilgrims]
-
A.
hasSpecialIndulgence
Indicates that one entity grants or possesses a particular privilege, exemption, or favor specifically afforded to another entity.
-
B.
hasNumberOfTemptations
Indicates the specific count of temptations associated with an entity or situation.
-
C.
allowsTastingOf
Indicates that one entity permits another entity to sample or try the taste of something.
-
D.
hasSpiciness
Indicates that one entity possesses a certain level or quality of spiciness in relation to another entity or a defined scale.
-
E.
hasTastingProfile
Indicates that an entity possesses a specific flavor or sensory profile, typically describing its characteristic tastes and aromas.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a12ccf481908f71f888cd744b64 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067da970481908a038995ba7dfb4b |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:49 p.m.