Triple
T3684248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Simeon the Myrrh-streaming |
E78185
|
entity |
| Predicate | miracleAttribute |
P41944
|
FINISHED |
| Object | myrrh flowing from relics |
—
|
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: myrrh flowing from relics | Statement: [Saint Simeon the Myrrh-streaming, miracleAttribute, myrrh flowing from relics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miracleAttribute Context triple: [Saint Simeon the Myrrh-streaming, miracleAttribute, myrrh flowing from relics]
-
A.
miracleDescription
chosen
Indicates that a miraculous event or phenomenon is being described or characterized.
-
B.
miraclePerformedBy
Indicates that a miraculous event is carried out or caused by a particular agent or entity.
-
C.
keyMiracle
Indicates that an event or action is regarded as a central or decisive miracle within a given context or narrative.
-
D.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
E.
enchantedBy
Indicates that one entity has cast or holds a magical enchantment over another 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc49644d08190866d6c5df9d2b48d |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.