Triple
T11273960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasily (Basil) the Blessed |
E266882
|
entity |
| Predicate | spiritualGift |
P29190
|
FINISHED |
| Object | prophecy |
—
|
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: prophecy | Statement: [Vasily (Basil) the Blessed, spiritualGift, prophecy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritualGift Context triple: [Vasily (Basil) the Blessed, spiritualGift, prophecy]
-
A.
spiritualityCharacteristic
Indicates that one entity possesses, exhibits, or is defined by a spiritual quality, trait, or aspect in relation to another.
-
B.
spiritualBenefit
Indicates a relationship where one entity provides, enhances, or is associated with a positive spiritual gain, growth, or advantage for another entity.
-
C.
spiritualMinistry
Indicates that one entity provides religious or spiritual guidance, care, or services to another entity.
-
D.
inTheSpiritOf
Indicates that one entity acts, is created, or is characterized in a manner that follows the style, principles, or intent exemplified by another entity.
-
E.
heldSpiritualPower
chosen
Indicates that an entity possessed or maintained spiritual or supernatural power in relation to another entity or context.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e965c9048190804ebb48f0a4817b |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.