Triple
T887297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Christology |
E19158
|
entity |
| Predicate | approachType |
P10782
|
FINISHED |
| Object | from-below Christology |
—
|
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: from-below Christology | Statement: [Low Christology, approachType, from-below Christology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachType Context triple: [Low Christology, approachType, from-below Christology]
-
A.
hasApproachType
chosen
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
-
B.
includesApproach
Indicates that one entity incorporates, utilizes, or is characterized by a particular method, strategy, or approach in relation to another entity or context.
-
C.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
D.
approachRoute
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
E.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
- 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.