Triple
T21772648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahmastra |
E537473
|
entity |
| Predicate | wielderRequirement |
P6204
|
FINISHED |
| Object | great spiritual discipline |
—
|
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: great spiritual discipline | Statement: [Brahmastra, wielderRequirement, great spiritual discipline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wielderRequirement Context triple: [Brahmastra, wielderRequirement, great spiritual discipline]
-
A.
requiresSkill
chosen
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
B.
requiresAttunementOriginal
Indicates that the item or effect necessitates attunement by a creature before its full properties or benefits can be used.
-
C.
weaponForgedFor
Indicates that a weapon was specifically created or crafted for a particular entity, purpose, or context.
-
D.
weaponProficiency
Indicates that an entity has the skill or qualification to effectively use a specified weapon.
-
E.
laterWielder
Indicates that one entity becomes the wielder or user of an object or power after another entity who wielded it earlier.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031af6a488190a2dcebed43d199d4 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.