Triple
T36560193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disputation XXVII |
E901813
|
entity |
| Predicate | hasRelationToAuthorCorpus |
—
|
GENERATED |
| Object | part of Suárez’s major metaphysical work |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationToAuthorCorpus Context triple: [Disputation XXVII, hasRelationToAuthorCorpus, part of Suárez’s major metaphysical work]
-
A.
relatedToAuthorCorpus
chosen
Indicates a general association or connection between something and the body of works (corpus) produced by a particular author.
-
B.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
C.
hasAuthorRelationshipToSubject
Indicates that an entity serves as the author or creator of the specified subject.
-
D.
subjectRelationToAuthor
Indicates the relationship or connection that the subject has to the author.
-
E.
hasPartOfCorpus
Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
- F. None of above.
Provenance (1 batch)
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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.