Triple
T11547633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venthyr |
E273810
|
entity |
| Predicate | covenantAbilityType |
P21124
|
FINISHED |
| Object | Class-specific signature abilities |
—
|
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: Class-specific signature abilities | Statement: [Venthyr, covenantAbilityType, Class-specific signature abilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covenantAbilityType Context triple: [Venthyr, covenantAbilityType, Class-specific signature abilities]
-
A.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
B.
ultimateAbility
Indicates that an entity possesses or uses its most powerful, defining special ability or move.
-
C.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
-
D.
typeOfPowerGranted
chosen
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
E.
benefitsFromCovenantWith
Indicates that one entity gains advantages, protections, or favorable outcomes as a result of being in a covenant relationship with 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.