Triple
T37515899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halondrus the Reclaimer |
E932631
|
entity |
| Predicate | lootRestriction |
P188199
|
FINISHED |
| Object | requires raid group to defeat |
—
|
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: requires raid group to defeat | Statement: [Halondrus the Reclaimer, lootRestriction, requires raid group to defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lootRestriction Context triple: [Halondrus the Reclaimer, lootRestriction, requires raid group to defeat]
-
A.
lootPreference
Indicates a relationship where one entity has a favored choice or priority regarding the distribution or selection of loot.
-
B.
lootTableIncludes
Indicates that a particular loot table contains or can yield a specified item or reward.
-
C.
LootType
Indicates the type or category of loot associated with an entity or event.
-
D.
redemptionRestriction
Indicates a limitation or condition placed on when, how, or to what extent something can be redeemed.
-
E.
hasAttackRestriction
Indicates that there is a limitation or condition placed on how, when, or whom an entity is allowed to attack.
- F. None of above. chosen
Provenance (4 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.