Triple
T37554355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightslayer Armor |
E933658
|
entity |
| Predicate | setCategory |
P164863
|
FINISHED |
| Object | Classic Tier set |
—
|
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: Classic Tier set | Statement: [Nightslayer Armor, setCategory, Classic Tier set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setCategory Context triple: [Nightslayer Armor, setCategory, Classic Tier set]
-
A.
settingCategory
Indicates the classification or type of context in which something is set or configured (e.g., grouping settings under a common category).
-
B.
categoryInSET
chosen
Indicates that an entity belongs to, or is classified within, a specified set or category.
-
C.
sampleCategory
Indicates that an item or instance belongs to, or is classified under, a particular sample category.
-
D.
createsCategory
Indicates that one entity establishes or brings into existence a new category for organizing or classifying other entities.
-
E.
enteredCategory
Indicates that an entity has moved into, joined, or been assigned to a particular category.
- 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_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.