Triple
T16787281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Botwulf of Thorney |
E408011
|
entity |
| Predicate | hasHagiographicSource |
P35890
|
FINISHED |
| Object | medieval Latin vitae |
—
|
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: medieval Latin vitae | Statement: [Saint Botwulf of Thorney, hasHagiographicSource, medieval Latin vitae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHagiographicSource Context triple: [Saint Botwulf of Thorney, hasHagiographicSource, medieval Latin vitae]
-
A.
hasTheologicalSourceIn
Indicates that something derives its theological basis, authority, or origin from a specified source.
-
B.
hasSacredText
Indicates that an entity possesses or is associated with a particular sacred or religious text.
-
C.
hasSourceTradition
Indicates that something originates from, or is derived within, a particular cultural, religious, intellectual, or historical tradition.
-
D.
scriptureOrLegendSource
chosen
Indicates that something is derived from, based on, or documented in a particular scripture or legendary source.
-
E.
hasMythSource
Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21b6a408190b0766138cc9a9ee2 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.