Triple
T37664932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crying Obsidian |
E937799
|
entity |
| Predicate | hasBlastResistance |
P188604
|
FINISHED |
| Object | 1200 |
—
|
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: 1200 | Statement: [Crying Obsidian, hasBlastResistance, 1200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBlastResistance Context triple: [Crying Obsidian, hasBlastResistance, 1200]
-
A.
blastResistance
chosen
Indicates the degree to which something can withstand or resist damage from an explosion or blast.
-
B.
hasBaseDefense
Indicates that an entity possesses a specified level or value of defensive capability in its default or starting state.
-
C.
isResistant
Indicates that an entity can withstand, oppose, or is not significantly affected by a specified force, influence, or agent.
-
D.
confersResistanceTo
Indicates that one entity provides or imparts resistance or reduced susceptibility to another entity against a specified agent, condition, or effect.
-
E.
hasArmorPlating
Indicates that one entity is equipped with or covered by protective armor plating in relation to another entity or context.
- 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.