Triple
T94189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filioque clause in the Nicene Creed |
E1892
|
entity |
| Predicate | defendedBy |
P957
|
FINISHED |
| Object | Roman Catholic magisterial documents |
—
|
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: Roman Catholic magisterial documents | Statement: [Filioque clause in the Nicene Creed, defendedBy, Roman Catholic magisterial documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendedBy Context triple: [Filioque clause in the Nicene Creed, defendedBy, Roman Catholic magisterial documents]
-
A.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
B.
protectedBy
chosen
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
C.
defendingChampion
Indicates that an entity currently holds a title or championship and is defending it against challengers.
-
D.
defendant
Indicates that an entity is the party accused or sued in a legal action or proceeding.
-
E.
typeOfDefense
Indicates the specific kind or category of defense employed or possessed in a given 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebb3da08190a8b82564f33cde3b |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.