Triple
T37459013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sneed's Old Shredder |
E930870
|
entity |
| Predicate | cardBackAvailability |
P86131
|
FINISHED |
| Object | Standard card back |
—
|
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 card back | Statement: [Sneed's Old Shredder, cardBackAvailability, Standard card back]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardBackAvailability Context triple: [Sneed's Old Shredder, cardBackAvailability, Standard card back]
-
A.
physicalCardsAvailable
Indicates that tangible, real-world card versions of an item or entity are obtainable or in stock.
-
B.
hasCardBack
chosen
Indicates that an entity possesses or is associated with a specific card back design or reverse side.
-
C.
cardPackAvailableIn
Indicates that a particular card pack can be obtained, accessed, or used within a specified context, location, or platform.
-
D.
hasNumberOfCards
Indicates that an entity is associated with a specific quantity of cards.
-
E.
cardBackInteraction
Indicates an interaction that occurs with or on the back side of a card, such as flipping, revealing, or otherwise engaging with that side.
- 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_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.