Triple
T28890830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oathbreakers of the Paths of the Dead |
E732687
|
entity |
| Predicate | cannotBeHarmedBy |
P100262
|
FINISHED |
| Object | ordinary weapons |
—
|
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: ordinary weapons | Statement: [Oathbreakers of the Paths of the Dead, cannotBeHarmedBy, ordinary weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeHarmedBy Context triple: [Oathbreakers of the Paths of the Dead, cannotBeHarmedBy, ordinary weapons]
-
A.
cannotBeDamagedBy
chosen
Indicates that one entity is immune to harm, injury, or degradation caused by another specified entity or factor.
-
B.
cannotBeDefeatedBy
Indicates that one entity is invulnerable to defeat by another specified entity or set of entities.
-
C.
cannotDieInHumanSense
Indicates that the entity is not subject to death or mortality in the way humans experience or understand it.
-
D.
survivesAttackBy
Indicates that one entity remains alive, intact, or functional after being subjected to an attack initiated by another entity.
-
E.
notImmortal
Indicates that the entity does not possess immortality and is subject to death or an end to its existence.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 7:55 a.m.