Triple
T15171717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | baptism of Harald Bluetooth |
E362501
|
entity |
| Predicate | involvesConversionFrom |
P116991
|
FINISHED |
| Object | Norse paganism |
—
|
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: Norse paganism | Statement: [baptism of Harald Bluetooth, involvesConversionFrom, Norse paganism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesConversionFrom Context triple: [baptism of Harald Bluetooth, involvesConversionFrom, Norse paganism]
-
A.
convertsFrom
Indicates that one entity is transformed or changed into another entity, with the source being the starting form or state.
-
B.
convertsTo
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
-
C.
allowsConversionTo
Indicates that one entity permits or enables transformation or change into another specified form or state.
-
D.
convertedFrom
Indicates that one entity has been transformed or changed in form, type, or representation from another entity.
-
E.
acceptsConversionFrom
Indicates that one entity can validly receive or handle a conversion from another entity’s type, format, or representation.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064ec56481909f11fa6e5686f076 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:09 a.m.