Triple
T3745185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miriam |
E81192
|
entity |
| Predicate | intercessorFor |
P51073
|
FINISHED |
| Object | Moses prayed for her healing |
—
|
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: Moses prayed for her healing | Statement: [Miriam, intercessorFor, Moses prayed for her healing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intercessorFor Context triple: [Miriam, intercessorFor, Moses prayed for her healing]
-
A.
initiator
Indicates the entity that starts, triggers, or causes an action, event, or process to occur.
-
B.
intermediaryType
Indicates the specific role or category of intermediary involved in facilitating the relationship or transaction between entities.
-
C.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
D.
facilitatedBy
Indicates that an action, process, or relationship occurs or is made easier through the assistance, support, or enabling role of a particular agent or mechanism.
-
E.
petitionerRole
Indicates the role or capacity in which a petitioner is acting within a legal or formal proceeding.
- F. None of above. chosen
Provenance (4 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb680ddc819094205beb342699f9 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc1560c248190b07438d766880990 |
completed | March 8, 2026, 6:35 p.m. |
Created at: March 8, 2026, 3:35 p.m.