Triple
T17764391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filioque controversy |
E443465
|
entity |
| Predicate | hasTheologicalField |
P25269
|
FINISHED |
| Object | Trinitarian 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: Trinitarian theology | Statement: [Filioque controversy, hasTheologicalField, Trinitarian theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTheologicalField Context triple: [Filioque controversy, hasTheologicalField, Trinitarian theology]
-
A.
theologicalField
chosen
Indicates that something pertains to or is categorized within a specific area or branch of theology.
-
B.
hasTheologicalMethod
Indicates a relationship where a subject employs, follows, or is characterized by a particular theological method or approach to doing theology.
-
C.
hasPhilosophicalField
Indicates that an entity is associated with, specializes in, or pertains to a particular branch or field of philosophy.
-
D.
theologicalCategory
Indicates the classification of something according to a particular theological type, tradition, or doctrinal category.
-
E.
hasAuthorTheologicalAffiliation
Indicates that an author is associated with a particular theological tradition, denomination, or belief system.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fb2a3c81908887d1d36aee942d |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.