Triple
T16321288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arian controversy |
E396296
|
entity |
| Predicate | involvesBeliefAbout |
P57220
|
FINISHED |
| Object | divinity of Christ |
—
|
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: divinity of Christ | Statement: [Arian controversy, involvesBeliefAbout, divinity of Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesBeliefAbout Context triple: [Arian controversy, involvesBeliefAbout, divinity of Christ]
-
A.
invokesBeliefIn
Indicates that one entity causes, triggers, or calls upon a belief or mental acceptance of something in another entity.
-
B.
basedOnBelief
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that entity.
-
C.
requiresBeliefIn
Indicates that one entity can only be valid, accessible, or fulfilled if belief in another specified entity or proposition is held.
-
D.
relatedBelief
Indicates that one belief is connected to, derived from, or otherwise associated with another belief in some meaningful way.
-
E.
believedTo
chosen
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b5f0f081909a5379deaf0df5d5 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.