Triple
T22478572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Constantinople 1351 |
E555699
|
entity |
| Predicate | endorsedDoctrine |
P14528
|
FINISHED |
| Object | Hesychast theology |
—
|
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: Hesychast theology | Statement: [Council of Constantinople 1351, endorsedDoctrine, Hesychast theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endorsedDoctrine Context triple: [Council of Constantinople 1351, endorsedDoctrine, Hesychast theology]
-
A.
encouragedDoctrine
Indicates that an entity actively promoted or urged others to adopt or follow a particular doctrine or set of beliefs.
-
B.
confirmedDoctrine
chosen
Indicates that an authority has officially validated, endorsed, or ratified a particular doctrine as true or acceptable.
-
C.
deniesDoctrine
Indicates that one entity rejects, opposes, or refuses to accept the truth or validity of a particular doctrine associated with another entity.
-
D.
followsDoctrine
Indicates that one entity adheres to, complies with, or acts in accordance with a specified doctrine or set of guiding principles.
-
E.
acceptsDoctrine
Indicates that one entity acknowledges, adopts, or agrees to follow the doctrine put forward by another entity.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be653bc8190a2e5c47e38228bfe |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.