Triple
T17764383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filioque controversy |
E443465
|
entity |
| Predicate | aroseOver |
P48990
|
FINISHED |
| Object | addition of Filioque to the Creed in the West |
—
|
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: addition of Filioque to the Creed in the West | Statement: [Filioque controversy, aroseOver, addition of Filioque to the Creed in the West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aroseOver Context triple: [Filioque controversy, aroseOver, addition of Filioque to the Creed in the West]
-
A.
raisedOn
Indicates that an entity was nurtured, brought up, or spent its formative period in a particular place, environment, or context.
-
B.
raisedAt
Indicates that something was brought up, mentioned, or initiated at a particular time, place, or contextual point.
-
C.
raisedDuring
Indicates that one entity was brought up, nurtured, or developed within the time period or circumstances defined by another entity.
-
D.
raisedFrom
Indicates that one entity has been elevated, derived, or brought up from another prior state, source, or condition.
-
E.
arisesIn
chosen
Indicates that something originates, emerges, or comes into existence within a specified context, source, or location.
- 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.