Triple
T37662202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Husk (Minecraft) |
E937740
|
entity |
| Predicate | canPickUpLoot |
P189100
|
FINISHED |
| Object | sometimes |
—
|
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: sometimes | Statement: [Husk (Minecraft), canPickUpLoot, sometimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canPickUpLoot Context triple: [Husk (Minecraft), canPickUpLoot, sometimes]
-
A.
wasLooted
Indicates that an entity was forcibly taken or plundered, typically during a theft, raid, or act of violence.
-
B.
requiresItemPickup
Indicates that an action, process, or condition cannot proceed or be fulfilled until a specified item has been physically picked up or collected.
-
C.
lootRestriction
Indicates a rule or limitation on what loot can be obtained, used, or distributed in a given context.
-
D.
bindsOnPickup
Indicates that an item becomes permanently bound to the entity that picks it up at the moment of pickup.
-
E.
lootPreference
Indicates a relationship where one entity has a favored choice or priority regarding the distribution or selection of loot.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:18 p.m.