Triple
T22836011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman of Bulgaria |
E565948
|
entity |
| Predicate | reasonForNoHeirs |
P41735
|
FINISHED |
| Object | castration |
—
|
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: castration | Statement: [Roman of Bulgaria, reasonForNoHeirs, castration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNoHeirs Context triple: [Roman of Bulgaria, reasonForNoHeirs, castration]
-
A.
hadNoLegitimateHeirs
Indicates that the person died without any legally recognized offspring who could inherit their title, property, or rights.
-
B.
reasonForNoGrave
Indicates the circumstance or explanation for why an individual does not have a grave or burial site.
-
C.
reasonForSuccession
Indicates the specific cause, circumstance, or justification that led one entity to succeed or replace another.
-
D.
hadNoSurvivingChildren
Indicates that the person did not have any children who were alive at the relevant point in time.
-
E.
reasonForLossOfSuccessionRights
chosen
Indicates the specific cause or circumstance that led to an individual losing their rights of succession.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2f09608190bc8e465e53b39e2e |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.