Triple
T23284226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven-Card Stud |
E588944
|
entity |
| Predicate | hiLoQualifier |
P13306
|
FINISHED |
| Object | 8-or-better in hi-lo split variant |
—
|
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: 8-or-better in hi-lo split variant | Statement: [Seven-Card Stud, hiLoQualifier, 8-or-better in hi-lo split variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiLoQualifier Context triple: [Seven-Card Stud, hiLoQualifier, 8-or-better in hi-lo split variant]
-
A.
hasQualifier
chosen
Indicates that one entity serves as a qualifier or modifier that further specifies or restricts the meaning or scope of another entity or statement.
-
B.
limitsPriorityOf
Indicates that one entity imposes a maximum allowable priority level on another entity’s priority.
-
C.
isHighestRangeOf
Indicates that one entity represents the maximum or topmost range or interval within which another entity falls or is categorized.
-
D.
hasLowerThroughputThan
Indicates that one entity’s throughput is less than that of another entity.
-
E.
isSecondHighest
Indicates that one entity ranks immediately below the highest-ranked entity within a specified ordering or set.
- 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:58 p.m.