Triple
T62546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atonement |
E1241
|
entity |
| Predicate | understoodAs |
P1120
|
FINISHED |
| Object | Christ dying for sins |
—
|
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: Christ dying for sins | Statement: [Atonement, understoodAs, Christ dying for sins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: understoodAs Context triple: [Atonement, understoodAs, Christ dying for sins]
-
A.
interpretedInCase
Indicates that something is understood, analyzed, or given meaning within the context of a particular case or specific situational scenario.
-
B.
recognizedAs
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
C.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
D.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
E.
considered
chosen
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a251f74b0881909ad89127b8171277 |
completed | Feb. 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69a24ea242c8819086fe00bf01e6523e |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.