Triple
T37665001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pigstep music disc |
E937800
|
entity |
| Predicate | lootRarityCategory |
P86164
|
FINISHED |
| Object | treasure |
—
|
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: treasure | Statement: [Pigstep music disc, lootRarityCategory, treasure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lootRarityCategory Context triple: [Pigstep music disc, lootRarityCategory, treasure]
-
A.
LootType
chosen
Indicates the type or category of loot associated with an entity or event.
-
B.
lootPreference
Indicates a relationship where one entity has a favored choice or priority regarding the distribution or selection of loot.
-
C.
includesRarities
Indicates that one entity contains or encompasses specific rare or uncommon items, features, or elements associated with another entity.
-
D.
rarity
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
E.
lootRestriction
Indicates a rule or limitation on what loot can be obtained, used, or distributed in 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e001c88190912781fa9a84f246 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.