Triple
T37462034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C’Thun Warrior |
E930940
|
entity |
| Predicate | typicalRoleInMeta |
—
|
GENERATED |
| Object | anti-aggro control deck |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRoleInMeta Context triple: [C’Thun Warrior, typicalRoleInMeta, anti-aggro control deck]
-
A.
typicalRole
chosen
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
roleInMeta
Indicates that one entity has a specific role or function within the context or metadata of another entity.
-
C.
roleInMetadata
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
D.
typicalAdditionalRole
Indicates that an entity commonly or characteristically holds an extra role or function in addition to its primary one.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:17 p.m.