Triple
T35221205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renaud of Hohenstaufen |
E1016958
|
entity |
| Predicate | hasMaternalLineage |
P40407
|
FINISHED |
| Object | Beatrice I, Countess of Burgundy |
E289441
|
NE 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: Beatrice I, Countess of Burgundy | Statement: [Renaud of Hohenstaufen, hasMaternalLineage, Beatrice I, Countess of Burgundy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaternalLineage Context triple: [Renaud of Hohenstaufen, hasMaternalLineage, Beatrice I, Countess of Burgundy]
-
A.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
B.
hasMatrilinealConnection
chosen
Indicates a relationship where one entity is connected to another through a line of descent traced exclusively through female ancestors.
-
C.
hasMotherOrigin
Indicates that an entity’s origin, source, or lineage is derived from or attributed to a mother entity.
-
D.
hasMaternalGrandmother
Indicates that an entity has a specific individual who is its mother’s mother.
-
E.
maternalAncestorOf
Indicates that one entity is an ancestor of another specifically through a chain of maternal (mother-to-child) relationships.
- F. None of above.
Provenance (4 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0205c0bff481908238a382459b3a93 |
completed | May 11, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4249fe919c8190bbc04b96f01ec632 |
completed | June 29, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_6a0205143f20819087ee31576835be26 |
completed | May 11, 2026, 4:34 p.m. |
Created at: May 3, 2026, 4:02 p.m.