Triple
T37961166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shulker Shell |
E947010
|
entity |
| Predicate | obtainingMethod |
P859
|
FINISHED |
| Object | killing Shulkers in End Cities |
—
|
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: killing Shulkers in End Cities | Statement: [Shulker Shell, obtainingMethod, killing Shulkers in End Cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obtainingMethod Context triple: [Shulker Shell, obtainingMethod, killing Shulkers in End Cities]
-
A.
obtains
Indicates that one entity comes into possession or control of another entity, typically through some action or process.
-
B.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
C.
obtainedByInMCU
Indicates that something is acquired or achieved by a character or entity within the Marvel Cinematic Universe (MCU).
-
D.
realizationMethod
Indicates the means, process, or technique by which something is carried out, implemented, or brought into effect.
-
E.
hasObservationMethod
Indicates that a particular method, technique, or procedure is used to perform or obtain an observation.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.