Triple
T37554817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frenzy |
E933669
|
entity |
| Predicate | hasRarityRange |
P153679
|
FINISHED |
| Object | from common to 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: from common to legendary | Statement: [Frenzy, hasRarityRange, from common to legendary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRarityRange Context triple: [Frenzy, hasRarityRange, from common to legendary]
-
A.
includesRarities
chosen
Indicates that one entity contains or encompasses specific rare or uncommon items, features, or elements associated with another entity.
-
B.
tieneRango
Indicates that one entity possesses, is assigned, or falls within a specific rank or range in relation to 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.
categoryRange
Indicates that a category or classification spans from a defined lower bound to an upper bound within a specified range.
-
E.
hasRangeCategory
Indicates that a property or measurement falls within a specified category or interval of possible values.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4:17 p.m.