Triple
T917368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorrowful Mysteries |
E19799
|
entity |
| Predicate | recitedWith |
P9966
|
FINISHED |
| Object | Rosary beads |
—
|
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: Rosary beads | Statement: [Sorrowful Mysteries, recitedWith, Rosary beads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recitedWith Context triple: [Sorrowful Mysteries, recitedWith, Rosary beads]
-
A.
narratedTo
Indicates that one entity tells or recounts a story, event, or information directly to another entity as the audience.
-
B.
recitationTradition
Indicates a relationship where a text, work, or content is transmitted or performed according to a particular established style, method, or lineage of recitation.
-
C.
performedWith
chosen
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
D.
memorizedBy
Indicates that some content, information, or material has been learned and retained in memory by a particular entity.
-
E.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b6755c488190b7f7848110e3ea2c |
completed | March 1, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69a4b292d3408190947cbc2f794cf8c5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.