Triple
T35628329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayley and Sasha Banks |
E1029516
|
entity |
| Predicate | teamNameVariant |
P183468
|
FINISHED |
| Object | The Boss ‘n’ Hug Connection |
—
|
NE NERFINISHED |
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: The Boss ‘n’ Hug Connection | Statement: [Bayley and Sasha Banks, teamNameVariant, The Boss ‘n’ Hug Connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamNameVariant Context triple: [Bayley and Sasha Banks, teamNameVariant, The Boss ‘n’ Hug Connection]
-
A.
teamName
Indicates the relationship that assigns or associates a specific name with a particular team.
-
B.
teamNameType
Indicates the type or category associated with a team's name (e.g., formal name, short name, nickname).
-
C.
teamNameRefersTo
Indicates that a given team name designates or refers to a specific team entity.
-
D.
team1LaterKnownAs
Indicates that the first team was later renamed to or became known by the identity of the second team.
-
E.
teamNameElement
Indicates that something is an element or component of a team's name.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:05 p.m.