Triple
T887310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Christology |
E19158
|
entity |
| Predicate | methodologicalEmphasis |
P1717
|
FINISHED |
| Object | historical reconstruction of Jesus |
—
|
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: historical reconstruction of Jesus | Statement: [Low Christology, methodologicalEmphasis, historical reconstruction of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodologicalEmphasis Context triple: [Low Christology, methodologicalEmphasis, historical reconstruction of Jesus]
-
A.
disciplinaryMethod
Indicates a method or approach used to discipline, correct, or control another party’s behavior.
-
B.
philosophicalMethod
Indicates the method, approach, or technique used in conducting philosophical inquiry or reasoning.
-
C.
researchApproach
chosen
Indicates the methodological strategy or set of methods used to conduct and structure a research activity or investigation.
-
D.
strategyEmphasis
Indicates an entity’s primary focus or priority within a broader strategy or plan.
-
E.
ideologicalEmphasis
Indicates a relationship where an entity places particular focus or priority on a specific ideology or set of ideological 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ae787bf081909533082ca013624a |
completed | March 1, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8ff8c48190a33b00acf65c1276 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.