Triple
T37462306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open the Waygate |
E930947
|
entity |
| Predicate | rewardCardRarity |
P7075
|
FINISHED |
| Object | Legendary |
—
|
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: Legendary | Statement: [Open the Waygate, rewardCardRarity, Legendary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardCardRarity Context triple: [Open the Waygate, rewardCardRarity, Legendary]
-
A.
cardRarityColor
Indicates the association between a card’s rarity level and the color used to represent that rarity.
-
B.
rewardCard
Indicates that one entity provides or is associated with a reward card (such as a loyalty or points card) for another entity.
-
C.
rarityPattern
Indicates a relationship where an entity follows a specific distribution or pattern of rarity across a set of items, instances, or conditions.
-
D.
rarity
chosen
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
E.
rarityReason
Indicates the underlying cause or justification for why something is considered rare.
- 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.