Triple
T38590096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elementium Reinforced Bulwark |
E932433
|
entity |
| Predicate | isHeroicVariantAvailable |
P191249
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Elementium Reinforced Bulwark, isHeroicVariantAvailable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHeroicVariantAvailable Context triple: [Elementium Reinforced Bulwark, isHeroicVariantAvailable, true]
-
A.
hasHeroicResponder
Indicates that an entity is associated with or supported by another entity that performs a heroic or emergency response action on its behalf.
-
B.
hasCommercialVariant
Indicates that an entity has a related version that is produced, marketed, or sold commercially.
-
C.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
D.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
-
E.
hasHeroicTheme
Indicates that something (such as a work, scene, or motif) embodies or prominently features a heroic theme or quality.
- F. None of above. chosen
Provenance (4 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.