Triple
T37458307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aggro Shaman |
E930853
|
entity |
| Predicate | resourceProfile |
P188944
|
FINISHED |
| Object | Low card draw reliance |
—
|
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: Low card draw reliance | Statement: [Aggro Shaman, resourceProfile, Low card draw reliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceProfile Context triple: [Aggro Shaman, resourceProfile, Low card draw reliance]
-
A.
profileType
Indicates the specific category or role classification assigned to a profile within a system.
-
B.
architectureProfile
Indicates the structural or organizational design characteristics that define how a system, product, or entity is built or arranged.
-
C.
profileRole
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
-
D.
systemProfileStandard
Indicates that a system’s configuration or characteristics conform to a defined standard profile.
-
E.
hasPerformanceProfile
Indicates that an entity is associated with a specific performance profile that characterizes its performance attributes or behavior.
- F. None of above. chosen
Provenance (4 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 3, 2026, 4:17 p.m.