Triple
T11659220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blaze |
E277080
|
entity |
| Predicate | rareDrop |
P77092
|
FINISHED |
| Object | Blaze Head (with certain mods or data packs) |
—
|
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: Blaze Head (with certain mods or data packs) | Statement: [Blaze, rareDrop, Blaze Head (with certain mods or data packs)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rareDrop Context triple: [Blaze, rareDrop, Blaze Head (with certain mods or data packs)]
-
A.
rarity
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
B.
collectibleIn
chosen
Indicates that one entity can be collected or obtained within the context, location, or container defined by another entity.
-
C.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
D.
isRarelyAwarded
Indicates that a particular award, honor, or recognition is given out infrequently or under uncommon circumstances.
-
E.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.