Triple
T37661476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End Ship |
E937725
|
entity |
| Predicate | primaryUniqueLoot |
P204315
|
FINISHED |
| Object | Elytra |
—
|
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: Elytra | Statement: [End Ship, primaryUniqueLoot, Elytra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUniqueLoot Context triple: [End Ship, primaryUniqueLoot, Elytra]
-
A.
secondaryUniqueLoot
Indicates that an entity provides an additional, distinct item drop that is separate from its primary loot.
-
B.
lootPreference
Indicates a relationship where one entity has a favored choice or priority regarding the distribution or selection of loot.
-
C.
luckyItem
Indicates that an item is believed to bring good fortune, advantage, or positive outcomes to the associated entity.
-
D.
LootType
Indicates the type or category of loot associated with an entity or event.
-
E.
lootRestriction
Indicates a rule or limitation on what loot can be obtained, used, or distributed in a given context.
- 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.