Triple
T16011151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crusher |
E388338
|
entity |
| Predicate | secondaryAttack |
P62597
|
FINISHED |
| Object | turning into a rock golem |
—
|
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: turning into a rock golem | Statement: [Crusher, secondaryAttack, turning into a rock golem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryAttack Context triple: [Crusher, secondaryAttack, turning into a rock golem]
-
A.
secondaryFire
Indicates the use or activation of an alternate or secondary mode of firing in a weapon or tool, distinct from its primary fire action.
-
B.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
C.
secondaryTarget
Indicates that an entity serves as an additional or subordinate target in relation to a primary target within a given context or action.
-
D.
resultOfSecondAttack
chosen
Indicates that an event or state occurs as a consequence of a second attack in a sequence of attacks.
-
E.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.