Triple
T37459263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Juggernaut |
E930876
|
entity |
| Predicate | relatedCard |
—
|
GENERATED |
| Object | Burrowing Mine |
—
|
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: relatedCard Context triple: [Iron Juggernaut, relatedCard, Burrowing Mine]
-
A.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
B.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
E.
relatedSuit
Indicates that one suit is associated or connected to another suit in a relevant or meaningful way.
- 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.