Triple
T26746277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasili the Blind |
E674410
|
entity |
| Predicate | causeOfEpithet |
P9593
|
FINISHED |
| Object | blinded during dynastic struggle |
—
|
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: blinded during dynastic struggle | Statement: [Vasili the Blind, causeOfEpithet, blinded during dynastic struggle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfEpithet Context triple: [Vasili the Blind, causeOfEpithet, blinded during dynastic struggle]
-
A.
reasonForEpithet
chosen
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
B.
hasMeaningOfEpithet
Indicates that one entity expresses or conveys the meaning or sense of another entity’s epithet.
-
C.
basisOfEpithet
Indicates that one entity serves as the reason or source for an epithet or descriptive name applied to another entity.
-
D.
etymologyReason
Indicates the reason, source, or origin explaining how or why a term acquired its particular etymology.
-
E.
languageOfEpithet
Indicates the language in which an epithet (such as a descriptive or honorary title) is expressed.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 3:51 a.m.