Triple
T30154357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilgrim |
E766482
|
entity |
| Predicate | burdenType |
P168495
|
FINISHED |
| Object | burden of sin |
—
|
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: burden of sin | Statement: [Pilgrim, burdenType, burden of sin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burdenType Context triple: [Pilgrim, burdenType, burden of sin]
-
A.
burdenFound
Indicates that a responsibility, obligation, or load has been identified as existing or resting upon a particular entity.
-
B.
overburdenType
Indicates the type or classification of overburden material associated with an entity or location.
-
C.
diseaseBurdenType
Indicates the type or category of burden (e.g., mortality, morbidity, economic impact) that a disease imposes.
-
D.
overburden
Indicates that one entity places an excessive load, demand, or responsibility on another, beyond what it can reasonably handle.
-
E.
burdenOfProofOn
Indicates that the responsibility to provide evidence or justification in a dispute or claim rests with a particular party.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed66ab48190928ceb36710c1ed2 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:20 p.m.