Triple
T32714642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaunilo of Marmoutiers |
E836488
|
entity |
| Predicate | critiquedWork |
P51069
|
FINISHED |
| Object | 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: Proslogion | Statement: [Gaunilo of Marmoutiers, critiquedWork, Proslogion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: critiquedWork Context triple: [Gaunilo of Marmoutiers, critiquedWork, Proslogion]
-
A.
commentaryWorkFor
Indicates that one entity performs commentary or analysis work on behalf of, or under employment/contract with, another entity.
-
B.
famousCritique
Indicates that one entity is a well-known critical assessment, review, or commentary about another entity.
-
C.
criticizedConstruct
chosen
Indicates that one entity expressed disapproval or negative judgment about another entity’s constructed work, idea, or creation.
-
D.
usedToCritique
Indicates that something is employed as a means to analyze, evaluate, or express disapproval of something else.
-
E.
visualWorkFor
Indicates a relationship where one entity creates, designs, or produces visual material (such as graphics, images, or visual assets) specifically for another entity or purpose.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:11 a.m.