Triple
T16218876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelagian controversy |
E393665
|
entity |
| Predicate | positionOfOpponents |
P75206
|
FINISHED |
| Object | affirmation of original sin |
—
|
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: affirmation of original sin | Statement: [Pelagian controversy, positionOfOpponents, affirmation of original sin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfOpponents Context triple: [Pelagian controversy, positionOfOpponents, affirmation of original sin]
-
A.
positionOpposed
chosen
Indicates that two entities hold positions or stances that are in direct conflict or opposition to each other.
-
B.
axisOpponentsAssisted
Indicates that the subject entity provided assistance or support to opponents of the Axis powers.
-
C.
opponentState
Indicates the condition or status that an opposing party or competitor is currently in within a given context or interaction.
-
D.
opponentStrategy
Indicates that one entity employs or represents a strategic plan specifically designed to counter or compete against another entity.
-
E.
opposingLocation
Indicates that two entities are located directly opposite each other, typically across a defined reference such as a street, corridor, or boundary.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e227f95de081908e1abe32d281dbe7 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.