Triple
T23284209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven-Card Stud |
E588944
|
entity |
| Predicate | upcardsPerPlayer |
P58671
|
FINISHED |
| Object | 4 face-up cards |
—
|
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: 4 face-up cards | Statement: [Seven-Card Stud, upcardsPerPlayer, 4 face-up cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upcardsPerPlayer Context triple: [Seven-Card Stud, upcardsPerPlayer, 4 face-up cards]
-
A.
usesMinimumCopiesPerCard
Indicates that there is a constraint specifying the minimum number of copies of each card that must be used or included in a given context.
-
B.
deckNumber
Indicates the specific deck or floor level associated with an entity within a multi-level structure or vehicle.
-
C.
hasNumberOfCards
chosen
Indicates that an entity is associated with a specific quantity of cards.
-
D.
numberOfDecks
Indicates the quantity of decks associated with or contained in an entity.
-
E.
playerCapacity
Indicates the maximum number of players that can simultaneously participate in or be accommodated by something (such as a game, session, or venue).
- 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.