Triple
T19723441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burning bush |
E473664
|
entity |
| Predicate | miraculousProperty |
P41944
|
FINISHED |
| Object | bush burned with fire but was not consumed |
—
|
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: bush burned with fire but was not consumed | Statement: [Burning bush, miraculousProperty, bush burned with fire but was not consumed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miraculousProperty Context triple: [Burning bush, miraculousProperty, bush burned with fire but was not consumed]
-
A.
miracleType
Indicates the specific category or kind of miracle associated with an event or entity.
-
B.
miracleOccurs
Indicates that an event takes place which is perceived as extraordinary, inexplicable by natural or scientific laws, and often attributed to a supernatural or divine cause.
-
C.
memorableProp
Indicates that something possesses a quality or feature that makes it easy to remember or likely to be recalled.
-
D.
miracleDescription
chosen
Indicates that a miraculous event or phenomenon is being described or characterized.
-
E.
miracleClaim
Indicates that an entity asserts or reports that a miraculous or supernatural event has occurred.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f64984819097882c44098b1643 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:46 p.m.