Triple
T33490843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicene party |
E857732
|
entity |
| Predicate | positionInControversy |
P28841
|
FINISHED |
| Object | anti-Arian |
—
|
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: anti-Arian | Statement: [Nicene party, positionInControversy, anti-Arian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInControversy Context triple: [Nicene party, positionInControversy, anti-Arian]
-
A.
locationOfControversy
Indicates the place or setting where a dispute, debate, or controversy occurs or is centered.
-
B.
controversialWithin
Indicates that something is the subject of significant disagreement, debate, or divided opinion within a specified group, community, or context.
-
C.
roleInControversy
chosen
Indicates the specific part, involvement, or function an entity has within a particular controversy or disputed situation.
-
D.
controversialBecause
Indicates that one entity is considered controversial specifically due to, or as a result of, its relationship with or association to another entity.
-
E.
controversialStatus
Indicates that the subject is associated with debate, dispute, or disagreement regarding its acceptance, validity, or appropriateness.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: May 1, 2026, 1:38 a.m.