Triple
T35809203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Angle |
E1035181
|
entity |
| Predicate | associatedMoveType |
—
|
GENERATED |
| Object | suplex‑heavy offense |
—
|
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: associatedMoveType Context triple: [Team Angle, associatedMoveType, suplex‑heavy offense]
-
A.
associatedWithMovement
Indicates a relationship where an entity is connected to, involved in, or influenced by a particular movement (e.g., social, political, artistic, or ideological).
-
B.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
C.
includesMovementType
Indicates that one entity encompasses or contains a specific type or category of movement associated with another entity.
-
D.
hasMoveType
chosen
Indicates that an action or move is associated with a specific type or category (such as elemental, functional, or classification-based).
-
E.
associatedMob
Indicates a relationship where one entity is linked or connected to a particular mob (mobile entity), typically as its counterpart, partner, or related unit.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.