Triple
T37459708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinkmaster Overspark (reprint-related theme) |
E930886
|
entity |
| Predicate | hasLegendaryGem |
P179658
|
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), hasLegendaryGem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendaryGem Context triple: [Tinkmaster Overspark (reprint-related theme), hasLegendaryGem, true]
-
A.
hasJewel
chosen
Indicates that one entity possesses, contains, or is adorned with a jewel in relation to another entity.
-
B.
isLegendaryForSet
Indicates that an entity is classified as a legendary item specifically within the context of a given set or collection.
-
C.
hasLegendsMaterial
Indicates that something includes, references, or is composed of legendary or myth-based material.
-
D.
hasLegendaryPokémon
Indicates that an entity (such as a location, trainer, or group) possesses, contains, or is associated with at least one Legendary Pokémon.
-
E.
isLegendaryStatus
Indicates that an entity possesses a legendary status, typically signifying exceptional rarity, renown, or significance within a given context.
- 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_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 4:17 p.m.