Triple
T11659447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elytra |
E277085
|
entity |
| Predicate | equipmentSlot |
P63771
|
FINISHED |
| Object | chest |
—
|
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: chest | Statement: [Elytra, equipmentSlot, chest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentSlot Context triple: [Elytra, equipmentSlot, chest]
-
A.
loadoutSlot
chosen
Indicates the specific equipment or item slot in which a particular piece of gear or object is placed within a loadout configuration.
-
B.
missionEquipment
Indicates that certain equipment is assigned to, used for, or associated with carrying out a specific mission.
-
C.
weaponMount
Indicates that one entity serves as a mounting point or support structure for attaching or holding a weapon on another entity.
-
D.
equipmentOption
Indicates that a particular piece or configuration of equipment is available or selected as an option in a given context.
-
E.
internalWeaponsBays
Indicates that an entity is equipped with weapons storage or launch systems housed within its internal structure rather than mounted externally.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.