Triple
T35628358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayley and Sasha Banks |
E1029516
|
entity |
| Predicate | tagTeamDynamic |
P86568
|
FINISHED |
| Object | combination of technical and high-flying offense |
—
|
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: combination of technical and high-flying offense | Statement: [Bayley and Sasha Banks, tagTeamDynamic, combination of technical and high-flying offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tagTeamDynamic Context triple: [Bayley and Sasha Banks, tagTeamDynamic, combination of technical and high-flying offense]
-
A.
teamDynamic
chosen
Indicates how members of a group interact, collaborate, and influence each other’s behavior and performance as a collective unit.
-
B.
teammateDynamicWith
Indicates a relationship where two entities are teammates whose interaction or collaboration changes over time or across contexts.
-
C.
teamTag
Indicates that an entity is associated with, labeled by, or belongs to a particular team.
-
D.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
E.
teamBase
Indicates that one entity serves as the primary or foundational team associated 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.