Triple
T37439929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matilda of Brunswick-Lüneburg |
E930385
|
entity |
| Predicate | paternalDynasticOrigin |
P19328
|
FINISHED |
| Object | Duchy of Saxony |
—
|
NE NERFINISHED |
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: Duchy of Saxony | Statement: [Matilda of Brunswick-Lüneburg, paternalDynasticOrigin, Duchy of Saxony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paternalDynasticOrigin Context triple: [Matilda of Brunswick-Lüneburg, paternalDynasticOrigin, Duchy of Saxony]
-
A.
originCountryOfPaternalLine
Indicates the country from which a person’s paternal family line (through the father’s side) originates.
-
B.
paternalHouse
chosen
Indicates the family house or lineage associated with a person's father.
-
C.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
D.
paternalLineageTitle
Indicates the title or designation an entity holds specifically through its paternal line of descent.
-
E.
patronymicOrigin
Indicates that one entity’s name is derived from the name of a father or paternal ancestor of another entity.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.