Triple
T25857599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter of Toledo |
E651390
|
entity |
| Predicate | sourceTypeTranslated |
P159536
|
FINISHED |
| Object | theological texts |
—
|
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: theological texts | Statement: [Peter of Toledo, sourceTypeTranslated, theological texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceTypeTranslated Context triple: [Peter of Toledo, sourceTypeTranslated, theological texts]
-
A.
translationSource
Indicates that one entity serves as the original text or content from which another entity is translated.
-
B.
languageTranslatedFrom
Indicates that a language is the source/original language from which content has been translated into another language.
-
C.
typeOfTranslation
Indicates that one entity is a specific kind or category of translation in relation to another entity.
-
D.
sourceLanguageMeaning
Indicates that one entity expresses the meaning or sense of another entity in a particular source language.
-
E.
possiblyTranslatedFrom
Indicates that one item may be a translation of another, but this relationship is uncertain or not definitively established.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60268b1388190b38c6d70cd028ecf |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:01 a.m.