Triple
T7044276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murphy MacManus |
E163589
|
entity |
| Predicate | usesPrayer |
P21327
|
FINISHED |
| Object | family prayer before executions |
—
|
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: family prayer before executions | Statement: [Murphy MacManus, usesPrayer, family prayer before executions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPrayer Context triple: [Murphy MacManus, usesPrayer, family prayer before executions]
-
A.
canBePrayed
Indicates that an entity is a suitable or valid target for prayer or religious supplication.
-
B.
praysAt
Indicates that one entity performs an act of prayer at, or directed toward, a specific place or site.
-
C.
praysBefore
Indicates that one entity performs an act of prayer earlier in time than another entity or event.
-
D.
associatedPrayer
chosen
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
E.
containsPrayerType
Indicates that one entity includes or encompasses a specific type or category of prayer.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.