Triple
T23284333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doyle Brunson |
E588946
|
entity |
| Predicate | reasonForCardHandNickname |
P7885
|
FINISHED |
| Object | won WSOP Main Event twice with Ten-Deuce |
—
|
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: won WSOP Main Event twice with Ten-Deuce | Statement: [Doyle Brunson, reasonForCardHandNickname, won WSOP Main Event twice with Ten-Deuce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCardHandNickname Context triple: [Doyle Brunson, reasonForCardHandNickname, won WSOP Main Event twice with Ten-Deuce]
-
A.
reasonForNickname
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
B.
reasonForName
chosen
Indicates the explanation or cause behind why an entity has a particular name.
-
C.
nicknameCategory
Indicates that one entity is a nickname and the other entity is the category or type that this nickname belongs to.
-
D.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for another entity.
-
E.
nicknameForRole
Indicates that one entity is an informal or alternative name commonly used to refer to a particular role or position represented by 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196454b4c8190a797537ce8912241 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:59 p.m.