Triple
T33413265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ad Florum |
E855644
|
entity |
| Predicate | writtenAgainst |
P176569
|
FINISHED |
| Object | opponents of Pelagianism |
—
|
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: opponents of Pelagianism | Statement: [Ad Florum, writtenAgainst, opponents of Pelagianism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenAgainst Context triple: [Ad Florum, writtenAgainst, opponents of Pelagianism]
-
A.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
B.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
C.
wrote
Indicates that an entity is the author or creator of a written work involving another entity.
-
D.
workWrittenFor
Indicates that a creative work was specifically composed, produced, or created for a particular person, group, event, purpose, or medium.
-
E.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:36 a.m.