Triple
T36470965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarum Use |
E898537
|
entity |
| Predicate | hasModernInterestFrom |
P192862
|
FINISHED |
| Object | liturgical scholars |
—
|
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: liturgical scholars | Statement: [Sarum Use, hasModernInterestFrom, liturgical scholars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernInterestFrom Context triple: [Sarum Use, hasModernInterestFrom, liturgical scholars]
-
A.
modernInterest
chosen
Indicates that an entity has a contemporary or current interest in, or engagement with, another entity or topic.
-
B.
hasHumanInterest
Indicates that something is of particular relevance, appeal, or concern to people, often engaging their emotions, curiosity, or personal experiences.
-
C.
hasNotableContemporary
Indicates that one entity is recognized as a significant or prominent contemporary (living or active in the same period) of another entity.
-
D.
hasContemporaryRecognition
Indicates that an entity is currently acknowledged, honored, or widely recognized in the present time or modern era.
-
E.
hasModernRelevance
Indicates that something maintains significance, applicability, or impact in contemporary times or current contexts.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4:10 p.m.