Triple
T16321293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arian controversy |
E396296
|
entity |
| Predicate | positionAffirmedByOpponents |
P122694
|
FINISHED |
| Object | the Son is begotten not made |
—
|
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: the Son is begotten not made | Statement: [Arian controversy, positionAffirmedByOpponents, the Son is begotten not made]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionAffirmedByOpponents Context triple: [Arian controversy, positionAffirmedByOpponents, the Son is begotten not made]
-
A.
positionOpposed
Indicates that two entities hold positions or stances that are in direct conflict or opposition to each other.
-
B.
allegedByOpponents
Indicates that a claim or accusation is made by opponents of the subject.
-
C.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
D.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
E.
consideredOpponentsAs
Indicates that one entity regarded or treated another entity as an opponent or adversary.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.