Triple
T31094390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodelinda |
E792484
|
entity |
| Predicate | convertedOrEncouragedConversionOf |
P141361
|
FINISHED |
| Object | Lombard nobility to Catholicism |
—
|
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: Lombard nobility to Catholicism | Statement: [Theodelinda, convertedOrEncouragedConversionOf, Lombard nobility to Catholicism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedOrEncouragedConversionOf Context triple: [Theodelinda, convertedOrEncouragedConversionOf, Lombard nobility to Catholicism]
-
A.
convertedIn
Indicates that one entity has been transformed, changed, or translated into another form, state, or representation within a specified context.
-
B.
hasConvertedTo
chosen
Indicates that an entity has changed its previous state, status, form, or affiliation into a new one.
-
C.
someConvertedTo
Indicates that a portion of one entity has been transformed or changed into another entity.
-
D.
involvesConversionTo
Indicates that one entity undergoes a change of form, type, or state resulting in another entity.
-
E.
allowsConversionTo
Indicates that one entity permits or enables transformation or change into another specified form or state.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 9:03 p.m.