Triple
T21087729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Spes Nostra |
E519545
|
entity |
| Predicate | roleOfMary |
P98876
|
FINISHED |
| Object | source of spiritual hope |
—
|
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: source of spiritual hope | Statement: [Maria Spes Nostra, roleOfMary, source of spiritual hope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfMary Context triple: [Maria Spes Nostra, roleOfMary, source of spiritual hope]
-
A.
motherRole
Indicates that one entity holds the role or function of a mother in relation to another entity.
-
B.
describesMaryAs
chosen
Indicates that one entity characterizes or portrays Mary in a particular way (e.g., with certain attributes, roles, or descriptions).
-
C.
playedMotherOfCharacter
Indicates that one person portrayed the mother of a specific character in a performance or production.
-
D.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
E.
relationshipToMary
Indicates that one entity stands in a specified personal or social relationship to Mary.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094be9388190b004fda23f301397 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.