Triple
T16160579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semi-Arianism |
E392165
|
entity |
| Predicate | consideredByOpponents |
P38117
|
FINISHED |
| Object | form of Arianism |
—
|
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: form of Arianism | Statement: [Semi-Arianism, consideredByOpponents, form of Arianism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredByOpponents Context triple: [Semi-Arianism, consideredByOpponents, form of Arianism]
-
A.
consideredOpponentsAs
Indicates that one entity regarded or treated another entity as an opponent or adversary.
-
B.
allegedByOpponents
chosen
Indicates that a claim or accusation is made by opponents of the subject.
-
C.
intendedOpponents
Indicates that one entity is the target or adversary that another entity is meant or designed to oppose or confront.
-
D.
consequenceForOpponents
Indicates that one party’s actions or status result in negative outcomes, penalties, or repercussions specifically for their opponents.
-
E.
sawOpponentsAs
Indicates perceiving or regarding certain entities as opponents or adversaries.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e5f0cb48190aae995d88382e055 |
completed | April 17, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.