Triple
T36282639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flavia Domitilla (the Younger’s daughter) |
E892979
|
entity |
| Predicate | possibleGrandmother |
P3524
|
FINISHED |
| Object | Flavia Domitilla the Elder |
—
|
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: Flavia Domitilla the Elder | Statement: [Flavia Domitilla (the Younger’s daughter), possibleGrandmother, Flavia Domitilla the Elder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleGrandmother Context triple: [Flavia Domitilla (the Younger’s daughter), possibleGrandmother, Flavia Domitilla the Elder]
-
A.
grandmother
chosen
Indicates that one entity is the female parent of another entity's parent.
-
B.
possibleGrandfatherOf
Indicates that one individual may be the grandfather of another, typically as the father of one of the other person’s parents, but with some uncertainty or lack of confirmation.
-
C.
grandparent
Indicates that one entity is the parent of another entity’s parent.
-
D.
greatGrandmother
Indicates that one person is the mother of another person's grandparent, i.e., a great-grandmother relationship.
-
E.
grandmotherInLaw
Indicates a relationship where one person is the grandmother of another person’s spouse.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.