Triple
T31192674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimson Dynamo |
E795222
|
entity |
| Predicate | firstCrimsonDynamoSpecialty |
P32672
|
FINISHED |
| Object | electronics |
—
|
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: electronics | Statement: [Crimson Dynamo, firstCrimsonDynamoSpecialty, electronics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCrimsonDynamoSpecialty Context triple: [Crimson Dynamo, firstCrimsonDynamoSpecialty, electronics]
-
A.
featuresSpecialAbility
Indicates that an entity possesses or is characterized by a particular special ability.
-
B.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
-
C.
wowSpecialization
Indicates that one entity has a specific specialization, role, or class within the context of World of Warcraft in relation to another entity.
-
D.
hasSpecial
chosen
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
E.
hasPowerDynamic
Indicates that there is an imbalance or structured hierarchy of influence, control, or authority between the related entities.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:08 p.m.