Triple
T10410042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silene |
E245363
|
entity |
| Predicate | resultOfLegend |
P89511
|
FINISHED |
| Object | conversion of inhabitants to Christianity |
—
|
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: conversion of inhabitants to Christianity | Statement: [Silene, resultOfLegend, conversion of inhabitants to Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfLegend Context triple: [Silene, resultOfLegend, conversion of inhabitants to Christianity]
-
A.
regionOfLegend
Indicates the geographic area or locale with which a particular legend or myth is associated.
-
B.
legend
Indicates that an entity is a traditional or historical story, figure, or narrative widely regarded as legendary rather than strictly factual.
-
C.
hasLegendAssociatedWith
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
D.
legendDetail
chosen
Indicates that additional explanatory or descriptive information is provided about a legend or key associated with another element.
-
E.
bestKnownLegend
Indicates that one entity is the most prominent or widely recognized legendary story or myth associated with another entity.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9fb98748190a3a6c161edd8f400 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:09 p.m.