Triple
T37661465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End Ship |
E937725
|
entity |
| Predicate | containsElytraLocation |
P123509
|
FINISHED |
| Object | item frame in ship interior |
—
|
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: item frame in ship interior | Statement: [End Ship, containsElytraLocation, item frame in ship interior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsElytraLocation Context triple: [End Ship, containsElytraLocation, item frame in ship interior]
-
A.
containsChestLocation
Indicates that one entity includes or encompasses the chest area as a specific sub-location within it.
-
B.
hasLanternMaterial
Indicates that an entity’s lantern is made from or composed of a specified material.
-
C.
hasWingIn
chosen
Indicates that an entity possesses a wing that is located in or contained within another specified entity or structure.
-
D.
hasWeaponBoxLocation
Indicates that an entity has a specific location associated with a weapon box.
-
E.
hasPylon
Indicates that one entity possesses, includes, or is equipped with a pylon as part of its structure or configuration.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01beacf8a88190ac643a75c7a0efc4 |
completed | May 11, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_6a01be152c8c8190bb19d64a683e2aae |
completed | May 11, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:18 p.m.