Triple
T37459704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinkmaster Overspark (reprint-related theme) |
E930886
|
entity |
| Predicate | digitalCard |
P115599
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tinkmaster Overspark (reprint-related theme), digitalCard, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalCard Context triple: [Tinkmaster Overspark (reprint-related theme), digitalCard, true]
-
A.
digitalCardGame
Indicates a relationship where a game is played using digital cards, typically involving virtual decks, rules, and interactions managed through software.
-
B.
hasDigitalCard
chosen
Indicates that an entity possesses or is associated with a digital card (such as an electronic ID, membership, or payment card).
-
C.
cardVariant
Indicates that one card is a specific version or variation of another base card.
-
D.
physicalCardColor
Indicates the relationship between a physical card and the color that characterizes its appearance.
-
E.
physicalCardMaterial
Indicates the material substance from which a physical card is made.
- 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.