Triple
T13681730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alma Redemptoris Mater |
E328018
|
entity |
| Predicate | requestsFromMary |
P34717
|
FINISHED |
| Object | to help the fallen people |
—
|
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: to help the fallen people | Statement: [Alma Redemptoris Mater, requestsFromMary, to help the fallen people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestsFromMary Context triple: [Alma Redemptoris Mater, requestsFromMary, to help the fallen people]
-
A.
mayRequest
Indicates that one entity is permitted or authorized to make a request to another entity or for a particular resource or action.
-
B.
requestedFrom
chosen
Indicates that one entity has made a request to another entity as the source or provider of something.
-
C.
requestedBy
Indicates that one entity has made a request for something to be done, provided, or obtained by another entity.
-
D.
requestType
Indicates the specific kind or category of request being made in an interaction or transaction.
-
E.
requestedRevisionsBy
Indicates that one entity has asked another entity to make changes or revisions to something.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.