Triple
T30210442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relics of the Virgin Mary |
E768051
|
entity |
| Predicate | attributedProperty |
P118612
|
FINISHED |
| Object | miracle-working power |
—
|
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: miracle-working power | Statement: [Relics of the Virgin Mary, attributedProperty, miracle-working power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attributedProperty Context triple: [Relics of the Virgin Mary, attributedProperty, miracle-working power]
-
A.
artifactProperty
chosen
Indicates that an artifact possesses a specific property, characteristic, or attribute.
-
B.
attributedDate
Indicates the date on which something is credited, assigned, or recorded as having occurred or been created.
-
C.
promisesAttributed
Indicates that a commitment or promise is ascribed to a particular entity as its source or author.
-
D.
targetProperty
Indicates that one entity serves as the intended goal, focus, or object of another entity’s action, influence, or effect.
-
E.
configurableProperty
Indicates that an entity has a setting or attribute whose value can be adjusted or customized, typically to modify its behavior or characteristics.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff0c0dc8190862a037439b36edf |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:32 p.m.