Triple
T38634951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Regina Angelorum |
E937550
|
entity |
| Predicate | honorsAttribute |
P60804
|
FINISHED |
| Object | Mary’s spiritual motherhood |
—
|
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: Mary’s spiritual motherhood | Statement: [Maria Regina Angelorum, honorsAttribute, Mary’s spiritual motherhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsAttribute Context triple: [Maria Regina Angelorum, honorsAttribute, Mary’s spiritual motherhood]
-
A.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
B.
honorsAspectOf
chosen
Indicates that one entity shows respect, recognition, or reverence specifically toward a particular aspect, quality, or facet of another entity.
-
C.
honorsStatus
Indicates that one entity recognizes, grants, or upholds a special honor or distinguished status associated with another entity.
-
D.
honorsRole
Indicates that one entity formally recognizes and respects the position, title, or role held by another entity.
-
E.
nameHonors
Indicates that a name is given to honor, commemorate, or pay tribute to a particular entity.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.