Triple
T30334361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loot (for Adventurers) |
E771575
|
entity |
| Predicate | mintType |
P161729
|
FINISHED |
| Object | free mint |
—
|
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: free mint | Statement: [Loot (for Adventurers), mintType, free mint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mintType Context triple: [Loot (for Adventurers), mintType, free mint]
-
A.
mint
Indicates the act of creating or issuing something new, typically in an official or authoritative capacity (such as producing new currency or tokens).
-
B.
typeOfMint
Indicates that one entity is a specific kind or variety of mint relative to another entity.
-
C.
mintageType
chosen
Indicates the specific method or category of production used when minting a coin or similar numismatic item.
-
D.
mintedFrom
Indicates that a newly created token, coin, or digital asset originates from or is derived directly from a specified source asset or input.
-
E.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681cad3f08190bf4224b74ea5852c |
completed | May 2, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:54 p.m.