Triple
T7096317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macedonianism |
E165336
|
entity |
| Predicate | responseLedTo |
P69330
|
FINISHED |
| Object | clearer formulation of the doctrine of the Holy Spirit |
—
|
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: clearer formulation of the doctrine of the Holy Spirit | Statement: [Macedonianism, responseLedTo, clearer formulation of the doctrine of the Holy Spirit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseLedTo Context triple: [Macedonianism, responseLedTo, clearer formulation of the doctrine of the Holy Spirit]
-
A.
responseLedBy
Indicates that a particular response, initiative, or action is directed, coordinated, or overseen by a specified leading entity.
-
B.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
-
C.
triggeredResponse
chosen
Indicates that one entity’s action or event causes another entity to produce a specific reaction or output.
-
D.
resolutionLeadsTo
Indicates that achieving a particular resolution or decision directly brings about or causes a subsequent outcome or state.
-
E.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e554d9f081909443be54eb501d25 |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.