Triple
T37459700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinkmaster Overspark (reprint-related theme) |
E930886
|
entity |
| Predicate | hasArtworkVariant |
P169777
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tinkmaster Overspark (reprint-related theme), hasArtworkVariant, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtworkVariant Context triple: [Tinkmaster Overspark (reprint-related theme), hasArtworkVariant, yes]
-
A.
hasCoverArtVariant
Indicates that an item has an alternative version of its cover artwork distinct from the primary cover.
-
B.
hasVariantDepiction
chosen
Indicates that one entity is depicted in an alternative or modified visual form relative to another depiction of the same subject.
-
C.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
D.
hasOfficialArtwork
Indicates that an entity is associated with an officially sanctioned piece of artwork representing it.
-
E.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
- 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_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 3, 2026, 4:17 p.m.