Triple
T37463494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter (Hearthstone class) |
E930976
|
entity |
| Predicate | deckSizeStandard |
P58671
|
FINISHED |
| Object | 30 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: 30 cards | Statement: [Hunter (Hearthstone class), deckSizeStandard, 30 cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deckSizeStandard Context triple: [Hunter (Hearthstone class), deckSizeStandard, 30 cards]
-
A.
deckNumber
Indicates the specific deck or floor level associated with an entity within a multi-level structure or vehicle.
-
B.
numberOfDecks
Indicates the quantity of decks associated with or contained in an entity.
-
C.
standardSetSize
Indicates that there is a defined or typical number of elements that constitute the standard size for a given set.
-
D.
cardSize
Indicates the specific dimensions or format assigned to a card within a given context or system.
-
E.
hasNumberOfCards
chosen
Indicates that an entity is associated with a specific quantity of cards.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.