Triple
T30736006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther Goddess Bast |
E782554
|
entity |
| Predicate | grantsPowerThrough |
P21124
|
FINISHED |
| Object | Heart-Shaped Herb ritual |
—
|
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: Heart-Shaped Herb ritual | Statement: [Panther Goddess Bast, grantsPowerThrough, Heart-Shaped Herb ritual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsPowerThrough Context triple: [Panther Goddess Bast, grantsPowerThrough, Heart-Shaped Herb ritual]
-
A.
grantedPower
Indicates that one entity has conferred authority, control, or a specific capability to another entity.
-
B.
typeOfPowerGranted
chosen
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
C.
believedToGrant
Indicates that something is thought or assumed to provide, confer, or bestow a particular benefit, quality, or effect.
-
D.
exercisedPowerAs
Indicates that one entity actively used or wielded authority, influence, or control in the capacity or role specified by another entity.
-
E.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 8:37 p.m.