Triple
T37461495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anomalus |
E930927
|
entity |
| Predicate | mechanicKeyword |
P48192
|
FINISHED |
| Object | Deathrattle |
—
|
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: Deathrattle | Statement: [Anomalus, mechanicKeyword, Deathrattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicKeyword Context triple: [Anomalus, mechanicKeyword, Deathrattle]
-
A.
mechanicTheme
Indicates a relationship where an entity serves as the theme or primary object affected in a mechanical action or process.
-
B.
mechanicalExpertise
Indicates that one entity possesses specialized knowledge or skill in understanding, operating, or repairing mechanical systems or devices in relation to another entity or context.
-
C.
featuresMechanic
chosen
Indicates that something includes or incorporates a particular mechanic as part of its design or functionality.
-
D.
mechanics
Indicates that an entity is involved in the study, design, or application of forces and motion (i.e., mechanical principles) in relation to another entity or system.
-
E.
mechanicRisk
Indicates that there is a potential danger, hazard, or adverse outcome associated with a particular mechanical process, operation, or mechanism.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:17 p.m.