Triple
T4064135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Death of Death in the Death of Christ |
E86283
|
entity |
| Predicate | argumentStyle |
P40578
|
FINISHED |
| Object | scholastic |
—
|
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: scholastic | Statement: [The Death of Death in the Death of Christ, argumentStyle, scholastic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: argumentStyle Context triple: [The Death of Death in the Death of Christ, argumentStyle, scholastic]
-
A.
commandStyle
Indicates the manner or approach in which one entity issues commands or directives to another.
-
B.
operatorStyle
Indicates the manner or approach an operator uses to perform or manage an operation, such as their method, technique, or behavioral style in carrying out tasks.
-
C.
syntaxStyle
Indicates the stylistic or structural conventions used in the form or arrangement of an expression, statement, or code.
-
D.
passingStyle
Indicates the manner or technique by which something (typically a ball or object) is passed from one entity to another.
-
E.
approachStyle
chosen
Indicates the manner or strategy with which one entity moves toward, engages with, or initiates interaction with another entity or target.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.