Triple
T33127624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palamite controversy |
E847761
|
entity |
| Predicate | hasDoctrinalOutcome |
P21672
|
FINISHED |
| Object | Palamism |
—
|
NE NERFINISHED |
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: Palamism | Statement: [Palamite controversy, hasDoctrinalOutcome, Palamism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoctrinalOutcome Context triple: [Palamite controversy, hasDoctrinalOutcome, Palamism]
-
A.
doctrinalOutcome
chosen
Indicates the result or consequence that follows from applying or adopting a particular doctrine, teaching, or set of beliefs.
-
B.
hasDoctrinalBasis
Indicates that one concept, claim, or practice is grounded in, supported by, or derived from a specific doctrine or set of doctrines.
-
C.
hasDoctrinalCharacteristic
Indicates that an entity possesses a specific doctrinal feature, quality, or attribute within a belief or teaching system.
-
D.
hasDoctrinalImplication
Indicates that one concept, statement, or action carries consequences or significance for a system of beliefs, teachings, or doctrines.
-
E.
hasDoctrinalDifferencesIn
Indicates that there are differences in doctrine or beliefs between entities within a specified domain 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:27 a.m.