Triple
T3285907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell |
E68979
|
entity |
| Predicate | roleInDoctrine |
P31678
|
FINISHED |
| Object | deterrent against 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: deterrent against sin | Statement: [Hell, roleInDoctrine, deterrent against sin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDoctrine Context triple: [Hell, roleInDoctrine, deterrent against sin]
-
A.
doctrineRole
chosen
Indicates the functional role or position an entity holds within a particular doctrine, teaching, or system of belief.
-
B.
proposesDoctrine
Indicates that one entity formally puts forward or advocates a particular doctrine, theory, or set of principles for consideration or adoption by others.
-
C.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
D.
appliedDoctrine
Indicates that a particular doctrine, principle, or rule has been put into practice or used in interpreting or deciding a specific case, situation, or context.
-
E.
developedDoctrine
Indicates that one entity created, formulated, or significantly advanced a particular doctrine or set of principles.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb03918c48190987d7cfd3bda9716 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.