Triple
T35809443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter Hearst Helmsley |
E1035189
|
entity |
| Predicate | ringDebutNameInWWF |
P156083
|
FINISHED |
| Object | Hunter Hearst Helmsley |
—
|
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: Hunter Hearst Helmsley | Statement: [Hunter Hearst Helmsley, ringDebutNameInWWF, Hunter Hearst Helmsley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ringDebutNameInWWF Context triple: [Hunter Hearst Helmsley, ringDebutNameInWWF, Hunter Hearst Helmsley]
-
A.
wrestlingRingName
Indicates the designated name or title assigned to a specific wrestling ring.
-
B.
ringDebut
Indicates the event or moment when an individual first competes or performs in a professional ring (such as in boxing, wrestling, or similar ring-based sports).
-
C.
wrestlerRingNameContext
chosen
Indicates that a particular ring name is used by a wrestler within a specific contextual setting, such as a promotion, time period, or storyline.
-
D.
madeWWEDebutAs
Indicates the role, persona, or capacity in which an individual first appeared in WWE.
-
E.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.