Triple
T38643946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Void Elves |
E938669
|
entity |
| Predicate | unlockRequirementType |
P160391
|
FINISHED |
| Object | Reputation grind |
—
|
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: Reputation grind | Statement: [Void Elves, unlockRequirementType, Reputation grind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlockRequirementType Context triple: [Void Elves, unlockRequirementType, Reputation grind]
-
A.
unlockType
Indicates the method or condition by which access to something is unlocked or made available.
-
B.
earnRequirementType
chosen
Indicates the type or category of requirement that must be fulfilled in order to earn or obtain something.
-
C.
ownershipRequirement
Indicates that a certain level or type of ownership must be held by an entity in order for a condition, action, or relationship to be valid or applicable.
-
D.
activationRequirement
Indicates the conditions or prerequisites that must be satisfied for an entity, process, or function to become active or operational.
-
E.
badgeRequirement
Indicates that one entity specifies the conditions or criteria that must be met to obtain or qualify for a particular badge associated with another entity.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.