Triple
T2812461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen |
E54201
|
entity |
| Predicate | mayBeMotherOf |
P20843
|
FINISHED |
| Object | Reigning monarch |
—
|
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: Reigning monarch | Statement: [Queen, mayBeMotherOf, Reigning monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeMotherOf Context triple: [Queen, mayBeMotherOf, Reigning monarch]
-
A.
possibleMother
chosen
Indicates that one entity could be the biological or adoptive mother of another, but this relationship is uncertain or not definitively established.
-
B.
possibleMotherOnly
Indicates that an entity is inferred or hypothesized to be the mother of another entity, but this relationship is not confirmed and remains only a possible maternal link.
-
C.
ancestorMother
Indicates that one entity is a female ancestor (mother, grandmother, etc.) of another entity in a family lineage.
-
D.
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.
-
E.
parentageIncludes
Indicates that a given parentage or lineage set contains or encompasses a particular parent or ancestral relationship.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde4a31d081909377044d5ff791b0 |
completed | March 7, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.