Triple
T37662003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wandering Trader (Minecraft) |
E937736
|
entity |
| Predicate | canBeAttackedBy |
P199692
|
FINISHED |
| Object | hostile mobs |
—
|
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: hostile mobs | Statement: [Wandering Trader (Minecraft), canBeAttackedBy, hostile mobs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAttackedBy Context triple: [Wandering Trader (Minecraft), canBeAttackedBy, hostile mobs]
-
A.
survivesAttackBy
Indicates that one entity remains alive, intact, or functional after being subjected to an attack initiated by another entity.
-
B.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
C.
oftenAttackedBy
Indicates that an entity is frequently the target of attacks carried out by another entity.
-
D.
cannotBeDamagedBy
Indicates that one entity is immune to harm, injury, or degradation caused by another specified entity or factor.
-
E.
isHuntedBy
Indicates that one entity is the target of hunting activity carried out by another entity.
- 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_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
| PDg | Predicate description generation | batch_69ff4fc5289c819084abd5ede185e96b |
completed | May 9, 2026, 3:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.