Triple
T37974623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Orkney |
E947386
|
entity |
| Predicate | motherOfMainLine |
P79450
|
FINISHED |
| Object | Queen Morgause |
—
|
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: Queen Morgause | Statement: [House of Orkney, motherOfMainLine, Queen Morgause]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherOfMainLine Context triple: [House of Orkney, motherOfMainLine, Queen Morgause]
-
A.
ancestorMother
Indicates that one entity is a female ancestor (mother, grandmother, etc.) of another entity in a family lineage.
-
B.
motherType
Indicates the specific category or role of motherhood that one entity has in relation to another (e.g., biological, adoptive, step).
-
C.
motherWas
chosen
Indicates that one entity was the mother (biological or adoptive) of another entity at some time in the past.
-
D.
motherMother
Indicates that one entity is the mother of another entity’s mother (i.e., the maternal grandmother relationship).
-
E.
motherInstanceOf
Indicates that a specific mother entity is an instance of a more general mother-related class or category.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.