Triple
T23840410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | robe of the Virgin Mary |
E590970
|
entity |
| Predicate | connectedToBelief |
P71815
|
FINISHED |
| Object | divine protection |
—
|
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: divine protection | Statement: [robe of the Virgin Mary, connectedToBelief, divine protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToBelief Context triple: [robe of the Virgin Mary, connectedToBelief, divine protection]
-
A.
linkedToBelief
chosen
Indicates that one entity is connected or associated with a particular belief, such that the belief influences, characterizes, or is attributed to that entity.
-
B.
relatedBelief
Indicates that one belief is connected to, derived from, or otherwise associated with another belief in some meaningful way.
-
C.
sharesBelief
Indicates that two or more entities hold the same belief or conviction.
-
D.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
E.
basedOnBelief
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c88797d4819081831fd3f8822ef4 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:08 p.m.