Triple
T887334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Christology |
E19158
|
entity |
| Predicate | evaluatedIn |
P13408
|
FINISHED |
| Object | ecumenical Christological discussions |
—
|
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: ecumenical Christological discussions | Statement: [Low Christology, evaluatedIn, ecumenical Christological discussions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluatedIn Context triple: [Low Christology, evaluatedIn, ecumenical Christological discussions]
-
A.
invokedIn
Indicates that an action, method, or function is called or executed within the context or body of another construct (such as a method, block, or scope).
-
B.
assessedBy
Indicates that an entity has been evaluated, examined, or judged by another entity (typically an agent or authority).
-
C.
executedWith
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
D.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
-
E.
usedInEnvironment
chosen
Indicates that something is utilized or operates within a particular environment 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_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.