Triple
T34554471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymond of Toledo |
E887163
|
entity |
| Predicate | languageOfEcclesiasticalWork |
P85137
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [Raymond of Toledo, languageOfEcclesiasticalWork, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfEcclesiasticalWork Context triple: [Raymond of Toledo, languageOfEcclesiasticalWork, Latin]
-
A.
languageOfReligion
Indicates the language in which a particular religion is traditionally expressed, practiced, or documented.
-
B.
hasClericalLanguage
Indicates that something is expressed using formal, religious, or church-related language or terminology.
-
C.
languageOfUnderlyingWork
chosen
Indicates the language in which the original or underlying work (from which a derived or related work stems) is expressed.
-
D.
languageOfGospelTraditionally
Indicates the language in which a particular Gospel is traditionally believed or held to have been written or transmitted.
-
E.
secondaryLanguageInLiturgy
Indicates that a particular language is used as a secondary (non-primary) language within a liturgical or worship context.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0075be7f54819081ab12bc1dab53bb |
completed | May 10, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a0073a19030819098c23faa3adcb96e |
completed | May 10, 2026, 12:01 p.m. |
Created at: May 1, 2026, 2:02 a.m.