Triple
T32210137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contra Severum |
E822775
|
entity |
| Predicate | polemicAgainst |
P153879
|
FINISHED |
| Object | teachings of Severus of Antioch |
—
|
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: teachings of Severus of Antioch | Statement: [Contra Severum, polemicAgainst, teachings of Severus of Antioch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polemicAgainst Context triple: [Contra Severum, polemicAgainst, teachings of Severus of Antioch]
-
A.
opposition
Indicates a relationship in which one entity actively resists, disagrees with, or is positioned against another entity, idea, or action.
-
B.
controversy
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
C.
aimsToRefute
chosen
Indicates an intention or effort by one entity to disprove, counter, or invalidate a claim, argument, or position held by another entity.
-
D.
ledAgainst
Indicates that one entity directed or commanded an opposing effort, campaign, or force against another entity.
-
E.
polarity
Indicates whether the relationship or statement is affirmed (positive) or denied/opposed (negative).
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb91c24481908bec766e2ed19345 |
completed | May 3, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:37 a.m.