Triple
T32670129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaunilo’s “On Behalf of the Fool” |
E835268
|
entity |
| Predicate | preservedWith |
P189358
|
FINISHED |
| Object | Anselm’s Proslogion |
—
|
NE NERFINISHED |
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: Anselm’s Proslogion | Statement: [Gaunilo’s “On Behalf of the Fool”, preservedWith, Anselm’s Proslogion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservedWith Context triple: [Gaunilo’s “On Behalf of the Fool”, preservedWith, Anselm’s Proslogion]
-
A.
preservedFor
Indicates that something has been kept intact or maintained in a particular state for the benefit, use, or reference of a specified entity or purpose.
-
B.
preservedFrom
Indicates that something has been protected or kept safe from a particular source of damage, loss, or alteration.
-
C.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
D.
somePreservedAs
Indicates that at least one part or instance of an entity is kept or maintained in a particular state, form, or condition.
-
E.
preservedExample
Indicates that an example instance has been kept intact or maintained in its original state for future reference or use.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 1, 2026, 1:09 a.m.