Triple
T36560193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disputation XXVII |
E901813
|
entity |
| Predicate | hasRelationToAuthorCorpus |
P196412
|
FINISHED |
| Object | part of Suárez’s major metaphysical work |
—
|
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: part of Suárez’s major metaphysical work | Statement: [Disputation XXVII, hasRelationToAuthorCorpus, part of Suárez’s major metaphysical work]
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 (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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.