Triple
T3369013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maud, Countess of Huntingdon |
E70907
|
entity |
| Predicate | paternalAncestry |
P41041
|
FINISHED |
| Object | Northumbrian nobility |
—
|
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: Northumbrian nobility | Statement: [Maud, Countess of Huntingdon, paternalAncestry, Northumbrian nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paternalAncestry Context triple: [Maud, Countess of Huntingdon, paternalAncestry, Northumbrian nobility]
-
A.
originCountryOfPaternalLine
Indicates the country from which a person’s paternal family line (through the father’s side) originates.
-
B.
paternalHouse
Indicates the family house or lineage associated with a person's father.
-
C.
patriarchalLineage
chosen
Indicates a familial relationship where descent, inheritance, or identity is traced through the male line or father’s ancestry.
-
D.
laterDiscoveredAncestry
Indicates that one entity learned about or confirmed an ancestral relationship or lineage only after an initial point in time or prior understanding.
-
E.
paternalGreatGrandmother
Indicates that one entity is the father’s father’s mother 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb28a813c81909d1c71fe577e6681 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.