Triple
T28612178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klondike |
E724191
|
entity |
| Predicate | usesDeckType |
P4066
|
FINISHED |
| Object | standard 52-card deck |
—
|
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: standard 52-card deck | Statement: [Klondike, usesDeckType, standard 52-card deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDeckType Context triple: [Klondike, usesDeckType, standard 52-card deck]
-
A.
hasDeckType
chosen
Indicates that an entity possesses or is associated with a specific type or category of deck.
-
B.
upperDeckUsedFor
Indicates that the upper deck of an object or structure is utilized for a specified purpose or activity.
-
C.
cardSetType
Indicates the classification relationship that specifies what type or category a given card set belongs to.
-
D.
isThroughDeck
Indicates that one object passes completely through another object or surface, extending from one side to the other.
-
E.
legalCardsFrom
Indicates that the referenced cards are permitted or valid according to the rules or constraints defined by the specified source or authority.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 4:30 a.m.