Triple
T13201698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Susanna |
E314256
|
entity |
| Predicate | familyBackgroundInLegend |
P13742
|
FINISHED |
| Object | noble Roman family |
—
|
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: noble Roman family | Statement: [Saint Susanna, familyBackgroundInLegend, noble Roman family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyBackgroundInLegend Context triple: [Saint Susanna, familyBackgroundInLegend, noble Roman family]
-
A.
familyBackgroundDetail
Indicates detailed information about an entity’s family background, such as lineage, upbringing, or familial circumstances.
-
B.
hasFamilyBackgroundIn
chosen
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
C.
loveInterestFamilyBackground
Indicates that information is being provided about the family background of a person's romantic partner or love interest.
-
D.
familyDescription
Indicates a descriptive statement that characterizes or summarizes the nature, structure, or dynamics of a family relationship.
-
E.
familyDesignation
Indicates the specific familial role or relationship label assigned to one entity in relation to another (e.g., parent, sibling, child).
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:16 p.m.