Triple
T22836031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman of Bulgaria |
E565948
|
entity |
| Predicate | motherFamilyBackground |
P13742
|
FINISHED |
| Object | Byzantine aristocracy |
—
|
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: Byzantine aristocracy | Statement: [Roman of Bulgaria, motherFamilyBackground, Byzantine aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherFamilyBackground Context triple: [Roman of Bulgaria, motherFamilyBackground, Byzantine aristocracy]
-
A.
familyBackgroundDetail
Indicates detailed information about an entity’s family background, such as lineage, upbringing, or familial circumstances.
-
B.
motherFounded
Indicates that a person, in her role as a mother, established or created an organization, institution, or entity.
-
C.
motherFrom
Indicates that one entity is the mother (biological or adoptive) of another entity, specifying a maternal parent-child relationship from the mother to the child.
-
D.
hasFamilyBackgroundIn
chosen
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
E.
motherFather
Indicates that the two entities are the biological parents (mother and father) of a child or offspring.
- 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.